No WiFi network available on Pi 3

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • No WiFi network available on Pi 3

      I have a Pi 3 and have downloaded the only image I can find from sourceforge.net/projects/openmediavault/files/ under "Raspberry Pi Images" the download was OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz

      Once installed and root password changed: no Wifi or wlan0 network is available, several tips on the forum advise on checking with ifconfig and even adding wlan0 config to the \etc\network... After numerous attempts and reinstalling a fresh image I'm still having no luck with any way to use WiFi.

      Upgraded/Updated install as well (using LAN) and it appears to now be on ver: 3.0.94 but again no luck on any form of WiFi adapter being recognized. I use the same Pi with other Jessie images and wifi is fine, even attempted nmtui-connect but it fails with ERROR as well.

      On boot, I notice on both installs, several FAIL messages in the boot sequence about "Arbitrary Executable File Format File System" as well as others that roll by too fast...
    • On sourceforge.net/projects/openm…/Raspberry%20Pi%20images/ there's clearly written:

      Source Code

      1. Write the .img.xz image in a single step using Etcher https://etcher.io
      2. to SD card. On first boot the installation will be finished. REMAIN PATIENT
      3. PLEASE since this can take up to 30 minutes with a slow SD card and slow
      4. internet connection (needs internet access to update all packages to latest
      5. version). After one automatic reboot green activity led stops blinking and
      6. then your Raspberry Pi is ready!
      Simply start over again, remain patient, wait for the reboot, enjoy OMV 3.0.94 without you needing to do anything (except waiting) and use Wi-Fi then (way too slow for data transfers anyway since crappy onboard antenna and 2.4GHz band only)
    • jeff.barclay wrote:

      Followed it step by step...
      Steps are
      1. burn image with Etcher
      2. connect Raspberry Pi to Ethernet (needs Internet connection on first boot)
      3. insert SD card, power on board, wait until green led stops blinking (this is after the reboot)
      4. check OMV UI, it has to report latest OMV 3 version (3.0.94 at the time of this writing) and latest RPi kernel version (something above 4.9.41)
      If step 4 displays anything else something with steps 1 to 3 went wrong (your Wi-Fi will never work) and you have to start over again. The above procedure is not important wrt Wi-Fi (since too slow anyway) but to get a fully working OMV install on Raspberries.
    • ok I have to admit I didn't wait for the reboot before logging in, however, this time with new SD card and fresh image, I waited (time was about 20 min.) and after reboot and root login, I'm still not showing wlan0 under network setting on web interface or CLI. Kernel is 4.9.59 ver 7 but OMV version is showing as 3.0.79 (Erasmus) it seemed to hang after the reboot at the BSD connection.
      Images
      • Screen Shot 2017-12-03 at 3.55.40 PM.png

        29.64 kB, 428×255, viewed 353 times
    • ok, after doing the "apt upgrade" the version is updated and with ifconfig its now showing the wlan0 for the first time. In the web interface its not showing but I think i'm close enough now. may be that since its not connected to wifi its not present.
      Images
      • Screen Shot 2017-12-03 at 4.16.32 PM.png

        29.67 kB, 431×257, viewed 306 times
      • Screen Shot 2017-12-03 at 4.19.45 PM.png

        27.66 kB, 873×256, viewed 378 times
    • jeff.barclay wrote:

      ok, after doing the "apt upgrade" the version is updated and with ifconfig its now showing the wlan0 for the first time. In the web interface its not showing but I think i'm close enough now. may be that since its not connected to wifi its not present.
      Did you add the wireless adapter in the Network Interfaces tab?
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Sorry for the user change from jell.barclay.

      After following your install instructions from 12/4 I have had a fully functional OMV working with a few glitches when trying to save changes - That being said, after running for about 2 weeks with little intervention, I was unable to ssh into it, permissions denied error after no conf changes - also became locked out of web interface several times. noted several "FALED boot up lines" the most notable was the ttyS1.service error that kept it from booting on several attempts.

      After hours of frustration I decided with numerous thing unstable to reinstalled on new SD CARD allowing for complete updates prior to login. After initial login, current version is 3.0.94 and kernel: 4.9.41-v7+

      Without any other changes I opened journalctl -xb and below is a condensed list of the errors on boot. I'm sure some are normal, but seems the ttyS1 seems to be a known issue is several forum users... can you help me understand which ones are acceptable to have and which ones could impact that stability of my install being a usable solution?

      Dec 16 12:15:50 omv kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
      Dec 16 12:15:50 omv kernel: [vc_sm_connected_init]: failed to initialize shared memory service
      Dec 16 12:15:50 omv kernel: [vc_sm_connected_init]: end - returning -1
      Dec 16 12:15:50 omv systemd[1]: Detected architecture 'arm'.
      Dec 16 12:15:50 omv systemd[1]: Failed to insert module 'ipv6'
      Dec 16 12:15:50 omv systemd[1]: Set hostname to <omv>.
      Dec 16 12:15:50 omv systemd-journal[173]: Journal started
      -- Subject: The Journal has been started
      -- Defined-By: systemd
      -- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- The system journal process has been starting up, opened the journal
      -- files for writing and is now ready to process requests.
      Dec 16 12:15:50 omv systemd-modules-load[129]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
      Dec 16 12:15:50 omv systemd-modules-load[129]: Failed to lookup alias 'fuse': Function not implemented
      Dec 16 12:15:50 omv systemd-modules-load[129]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
      Dec 16 12:15:50 omv systemd-modules-load[129]: Failed to lookup alias 'mv_cesa': Function not implemented
      Dec 16 12:15:50 omv systemd-modules-load[129]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
      Dec 16 12:15:50 omv systemd-modules-load[129]: Failed to lookup alias 'r8152': Function not implemented
      Dec 16 12:15:50 omv systemd-modules-load[129]: could not open moddep file '/lib/modules/4.9.41-v7+/modules.dep.bin'
      Dec 16 12:15:50 omv systemd-modules-load[129]: Failed to lookup alias 'ax88179_178a': Function not implemented
      Dec 16 12:15:50 omv systemd[1]: Mounted Configuration File System.
      Dec 16 12:15:51 omv systemd[1]: udev-finish.service: main process exited, code=exited, status=2/INVALIDARGUMENT
      Dec 16 12:15:51 omv kernel: EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
      Dec 16 12:15:51 omv systemd[1]: Failed to start Copy rules generated while the root was ro.
      -- Subject: Unit udev-finish.service has failed


      Dec 16 12:16:09 omv rpcbind[1080]: cannot create socket for udp6
      Dec 16 12:16:09 omv rpcbind[1080]: cannot create socket for tcp6
      --
      -- Unit lirc.service has begun starting up.
      Dec 16 12:16:11 omv smartd[1135]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
      Dec 16 12:16:11 omv systemd[1]: zram-config.service: main process exited, code=exited, status=1/FAILURE
      Dec 16 12:16:11 omv systemd[1]: Failed to start Initializes zram swaping.

      Dec 16 12:16:11 omv systemd[1]: Unit zram-config.service entered failed state.
      --
      -- The start-up result is done.
      Dec 16 12:16:11 omv acpid[1198]: cannot open input layer

      Dec 16 12:16:11 omv ntpd[1263]: restrict: error in address '::' on line 20. Ignoring...
      Dec 16 12:16:11 omv ntpd[1263]: restrict: error in address '::1' on line 23. Ignoring...

      Dec 16 12:16:11 omv snmpd[1163]: Starting SNMP services::pcilib: Cannot open /proc/bus/pci
      Dec 16 12:16:11 omv snmpd[1202]: pcilib: Cannot find any working access method.
      Dec 16 12:16:11 omv snmpd[1202]: pcilib: pci_init failed
      Dec 16 12:16:11 omv postfix/sendmail[1311]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol
      Dec 16 12:16:12 omv avahi-daemon[1109]: Server startup complete. Host name is omv.local. Local service cookie is 3886538412.
      Dec 16 12:16:12 omv systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.
      -- Subject: Unit openmediavault-engined.service has finished start-up
      -- Defined-By: systemd
      -- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- Unit openmediavault-engined.service has finished starting up.
      Dec 16 12:16:12 omv smartd[1135]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (260 bytes) to STDOUT/STDERR:
      Dec 16 12:16:12 omv smartd[1135]: /etc/smartmontools/run.d/10mail:
      Dec 16 12:16:12 omv smartd[1135]: send-mail: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol
      Dec 16 12:16:12 omv smartd[1135]: postdrop: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol


      Dec 16 12:16:12 omv systemd[1]: Failed to mount Arbitrary Executable File Formats File System.

      Dec 16 12:17:19 omv systemd[1]: Timed out waiting for device dev-ttyS1.device.
      -- Subject: Unit dev-ttyS1.device has failed

      -- The result is timeout.
      Dec 16 12:17:19 omv systemd[1]: Dependency failed for Serial Getty on ttyS1.
      -- Subject: Unit serial-getty@ttyS1.service has failed
      -- Defined-By: systemd
      -- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- Unit serial-getty@ttyS1.service has failed.

      Dec 16 12:32:28 omv openmediavault-webgui[1850]: Authorized login from 10.0.0.201 [username=admin, user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13) AppleWebKit/604.1.38 (KHTML, li
    • 1 no
      2 no it was sitting dormant
      3 I did but thats not to say the card was not corrupt.

      the log I posted id from a fresh install on a new SD card! - every install I do ends up with the same results... are there supposed to be "some" errors based on versions of the Pi or should every boot be without errors?
    • tkaiser wrote:

      Steps are
      1. burn image with Etcher
      2. connect Raspberry Pi to Ethernet (needs Internet connection on first boot)
      3. insert SD card, power on board, wait until green led stops blinking (this is after the reboot)
      4. check OMV UI, it has to report latest OMV 3 version (3.0.94 at the time of this writing) and latest RPi kernel version (something above 4.9.41)
      If step 4 displays anything else something with steps 1 to 3 went wrong (your Wi-Fi will never work) and you have to start over again. The above procedure is not important wrt Wi-Fi (since too slow anyway) but to get a fully working OMV install on Raspberries.
      1. check
      2. check
      3. check yesterday he had about 6H time

      i will try it again

      the installation with or without the wifi dongle?

      The post was edited 1 time, last by Fornax ().

    • Fornax wrote:

      i cant see the Wifi dongle attached to the raspberry under ifconfig
      Why does everyone plays around with ifconfig? Better check/provide the output of

      Source Code

      1. lsusb
      2. iwconfig
      3. dmesg
      4. nmtui-connect
      If your dongle is supported by the RPi kernel then the last command should allow you to join a wireless network: New approach for Raspberry Pi OMV images (and if you then connect your board with both Wi-Fi and Ethernet to the same network you'll run into funny problems later once you disconnect Ethernet :) )
    • tkaiser wrote:

      Why does everyone plays around with ifconfig?

      Experience with other solution, better or worst i dont know, just wanted to express thats on other solutions it worked and how.

      tkaiser wrote:

      Source Code

      1. lsusb
      2. iwconfig
      3. dmesg
      4. nmtui-connect

      Source Code

      1. Bus 001 Device 008: ID 0bc2:3300 Seagate RSS LLC
      2. Bus 001 Device 007: ID 0bc2:3323 Seagate RSS LLC
      3. Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
      4. Bus 001 Device 014: ID 148f:7601 Ralink Technology, Corp.
      5. Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
      6. Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
      7. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


      Source Code

      1. eth0 no wireless extensions.
      2. lo no wireless extensions.


      Source Code

      1. [14018.286247] usb 1-1.4: USB disconnect, device number 11
      2. [16384.182921] usb 1-1.2: new high-speed USB device number 12 using dwc_otg
      3. [16385.472871] usb 1-1.4: new high-speed USB device number 13 using dwc_otg
      4. [16386.522924] usb 1-1.2: new high-speed USB device number 14 using dwc_otg
      5. [16386.664842] usb 1-1.2: New USB device found, idVendor=148f, idProduct=7601
      6. [16386.664859] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      7. [16386.664867] usb 1-1.2: Product: 802.11 n WLAN
      8. [16386.664874] usb 1-1.2: Manufacturer: MediaTek
      9. [16386.664881] usb 1-1.2: SerialNumber: 1.0
      10. [16386.872838] usb 1-1.2: reset high-speed USB device number 14 using dwc_otg

      Source Code

      1. nmtui:ERROR:nmt-newt-listbox.c:333:update_active_internal: assertion failed: (priv->active >= 0 && priv->active < priv->entries->len)
      2. Aborted