Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: wlan0 does not exist / WIFI Linksys USB adapter
#1
Hi

Would anyone have some info to get a USB WIFI network detected?  
Basically wlan0 is not in the network interface undifined for some reason , although the device is present. 
Also i made sure the Access Point is not left blank,, added the SSID info
Eth0 is working good, and connected
Im pretty sure it has to be a simple step missed , my first time using Moode.
I have put as much information sorry its a bit long thread.

cat  /etc/wpa_supplicant/wpa_supplicant.conf
#########################################
# This file is automatically generated by
# the player Network configuration page.
#########################################

country=SE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="MYSSID"
scan_ssid=1

}




Moode system log::
20180605 215648 worker: File check ok
   20180605 215648 worker: - Network
   20180605 215648 worker: eth0 exists
   20180605 215649 worker: eth0 (10.50.1.106)
   20180605 215649 worker: wlan0 does not exist
   20180605 215649 worker: - Audio
   20180605 215649 worker: ALSA outputs unmuted
   20180605 215649 worker: Audio out (I2S audio device)
   20180605 215649 worker: Audio dev (Allo Boss DAC)
   20180605 215649 worker: ALSA mixer name (Digital)
   20180605 215649 worker: MPD volume control (software)
   20180605 215649 worker: Hdwr volume controller exists
   20180605 215650 worker: Chip options (Burr Brown PCM5122)
   20180605 215650 worker: - Services
   20180605 215652 worker: MPD started
   20180605 215652 worker: MPD scheduler policy (time-share)
   20180605 215652 worker: Configure MPD outputs

ifconfig

pi@moode:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.50.1.106  netmask 255.255.255.0  broadcast 10.50.1.255
        inet6 fe80::54:d5a9:fd5b:be4a  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:1a:85:90  txqueuelen 1000  (Ethernet)
        RX packets 526  bytes 113353 (110.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 870  bytes 989104 (965.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 192  bytes 17410 (17.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 192  bytes 17410 (17.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



## no wireless detected for wlan0 
pi@moode:~ $ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.




# here i can see the Bus detected the Device 5 ok 
pi@moode:~ $ lsusb
Bus 001 Device 005: ID 13b1:0042 Linksys
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub




syslog  Moode kernel detects the USB but with other manufacturer name instead of Linksys.. 
mtp.probe notes its not MTP device which is ok i guess.

Jun  5 20:57:23 moode kernel: [ 1732.109196] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
Jun  5 20:57:23 moode kernel: [ 1732.240510] usb 1-1.5: New USB device found, idVendor=13b1, idProduct=0042
Jun  5 20:57:23 moode kernel: [ 1732.240525] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun  5 20:57:23 moode kernel: [ 1732.240533] usb 1-1.5: Product: USBWLAN
Jun  5 20:57:23 moode kernel: [ 1732.240540] usb 1-1.5: Manufacturer: Qualcomm Atheros
Jun  5 20:57:23 moode kernel: [ 1732.240547] usb 1-1.5: SerialNumber: 12345678
Jun  5 20:57:23 moode mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5"
Jun  5 20:57:23 moode mtp-probe: bus: 1, device: 6 was not an MTP device



Also noticed the file is missing the wlan0 server which is controlled by the moode application.. not sure if i should edit and add what PI recommends the default for auto detect etc.

--
auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

--


/etc/network/interfaces

pi@moode:~ $ cat /etc/network/interfaces
#########################################

# This file is automatically generated by

# the player Network configuration page.

#########################################



# interfaces(5) file used by ifup(8) and ifdown(8)



# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'


# Include files from /etc/network/interfaces.d:

! no files in [b]/etc/network/interfaces.d  also!
[/b]


DUMP OF ALL SYSLOG MOODE WITH VERSIONS ETC.

S Y S T E M    P A R A M E T E R S  

Date and time = 2018-06-05 22:00:24
System uptime = up 3 minutes
Timezone = Europe/Stockholm
moOde = Release 4.1 2018-04-02

Host name = moode
ETH0  IP = 10.50.1.106
ETH0  MAC = b8:27:eb:1a:85:90
WLAN0 IP = unassigned
WLAN0 MAC = no adapter
WiFi country = SE

HDWR REV = Pi-2B 1GB v1.1
SoC = BCM2835
CORES = 4
ARCH = armv7l
RASPBIAN = 9.4
KERNEL = 4.14.32-v7+
KTIMER FREQ = 100 Hz
USB BOOT = not available
Warranty = OK

ROOT size = 15G
ROOT used = 17%
ROOT avail = 12G
FS expand = expanded
MEM free = 713 MB
MEM used = 52 MB
Temperature = 45.5°C

CPU GOV = performance
MPD SCHDPOL = TS
P3-WIFI = None
P3-BT = None
HDMI = On
ETH0 CHECK = On
MAX USB CUR = Off
UAC2 FIX = Off
SSH server = Off

LED0 = on
LED1 = on

 C O R E    S E R V E R S  

PHP-FPM = 7.0.27
NGINX = 1.10.3
SQLite = 3.16.2
Bluetooth = 5.49

 C P U    L O A D  

CPU %usr %sys %idle
all 0.25 0.00 99.75
0 0.00 0.00 100.00
1 0.00 0.00 100.00
2 1.00 0.00 99.00
3 0.00 0.00 100.00

 P R O C E S S    L O A D  

PRI RTPRIO COMMAND         %MEM PSR %CPU
19      - sysinfo.sh       0.2   2  2.6
19      - php-fpm7.0       1.3   3  1.7
19      - systemd          0.6   3  1.6
19      - sudo             0.3   3  0.6
19      - kworker/2:1      0.0   2  0.5
19      - worker.php       1.1   2  0.5
19      - systemd-journal  0.4   0  0.4
19      - systemd-udevd    0.3   0  0.3
19      - mmcqd/0          0.0   1  0.2

 C L O C K    F R E Q U E N C I E S  

    arm   = 900 MHz       pwm   = 0 MHz
    core  = 250 MHz       emmc  = 200 MHz
    h264  = 250 MHz       pixel = 148 MHz
    isp   = 250 MHz       vec   = 0 MHz
    v3d   = 250 MHz       hdmi  = 163 MHz
    uart  = 47 MHz       dpi   = 0 MHz

SD card = 50 MHz

 S Y S T E M    V O L T A G E S  

core = 1.3125V
sdram controller = 1.2000V
sdram I/O = 1.2000V
sdram chip = 1.2250V

 U I  C U S T O M I Z A T I O N S  

Theme = Standard
Accent color = Bluejeans
Alpha blend = 0.90
Adaptive background = Yes
Background image = No
Playback history = No
Extra metadata = Yes
Library = Use Artist

 A U D I O    P A R A M E T E R S  

Audio device = Allo Boss DAC
Interface = I2S
Hdwr volume = 100
Mixer name = Digital
Output stream = Closed
ALSA version = 1.1.3-5+rpi3
SoX version = 0.1.2-2

Volume knob = 87
Volume mute = Unmuted

Bluetooth controller = Off
Airplay receiver = On
Squeezelite = Off
UPnP renderer = Off
DLNA server = Off

Rotary encoder = Off
Encoder params = 100 2 3 4 5
Crossfeed = Off
Parametric EQ = Off
Graphic EQ = Off
Auto-shuffle = Off
Autoplay = Off
MPD crossfade = Off

 M P D    S E T T I N G S  

Version = 0.20.18
Volume control = software
ALSA device = hw:0
SoX resampling = disabled
SoX quality = very high
SoX multithreading = off
Audio buffer (kb) = 4096
Buffer before play = 10%
Output buffer size (kb) = 81920
Volume normalization = no
DSD over PCM (DoP) = no
Replay gain = off

 A I R P L A Y    S E T T I N G S  

Version = 3.1.7
Friendly name = Moode Airplay
ALSA device = hw:0
Volume mixer = auto
Resume MPD after = No
Output bit depth = S16
Output sample rate = 44100
Session interruption = no
Session timeout (ms) = 120
Audio buffer (secs) = 0.0

 S Q U E E Z E L I T E    S E T T I N G S  

Version = 1.8.7-1052 "DSD/SRC enabled"
Friendly name = Moode
ALSA device = hw:0
ALSA params = 80:4::1
Output buffers = 40000:100000
Task priority = 45
Codec list = flac,pcm,mp3,ogg,aac,alac,dsd
Other options = -W -D 500 -R E

 M O O D E    L O G  

   20180605 215645 worker: - Start
   20180605 215645 worker: Successfully daemonized
   20180605 215645 worker: - Init
   20180605 215646 worker: Session loaded
   20180605 215646 worker: Debug logging (on)
   20180605 215648 worker: Host (moode)
   20180605 215648 worker: Hdwr (Pi-2B 1GB v1.1)
   20180605 215648 worker: Arch (armv7l)
   20180605 215648 worker: Rasp (9.4)
   20180605 215648 worker: Kver (4.14.32-v7+)
   20180605 215648 worker: Ktyp (Standard)
   20180605 215648 worker: Gov  (performance)
   20180605 215648 worker: Rel  (Moode 4.1 2018-04-02)
   20180605 215648 worker: Upd  (None)
   20180605 215648 worker: MPD  (0.20.18)
   20180605 215648 worker: USB boot not enabled yet
   20180605 215648 worker: File system expanded
   20180605 215648 worker: HDMI port on
   20180605 215648 worker: File check ok
   20180605 215648 worker: - Network
   20180605 215648 worker: eth0 exists
   20180605 215649 worker: eth0 (10.50.1.106)
   20180605 215649 worker: wlan0 does not exist
   20180605 215649 worker: - Audio
   20180605 215649 worker: ALSA outputs unmuted
   20180605 215649 worker: Audio out (I2S audio device)
   20180605 215649 worker: Audio dev (Allo Boss DAC)
   20180605 215649 worker: ALSA mixer name (Digital)
   20180605 215649 worker: MPD volume control (software)
   20180605 215649 worker: Hdwr volume controller exists
   20180605 215650 worker: Chip options (Burr Brown PCM5122)
   20180605 215650 worker: - Services
   20180605 215652 worker: MPD started
   20180605 215652 worker: MPD scheduler policy (time-share)
   20180605 215652 worker: Configure MPD outputs
   20180605 215652 readMpdResponse(): reading response
   20180605 215652 readMpdResponse(): success $str=(OK MPD 0.20.0)
   20180605 215652 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
   20180605 215652 readMpdResponse(): reading response
   20180605 215652 readMpdResponse(): success $str=(OK)
   20180605 215652 readMpdResponse(): success $resp[0]=(outputid: 0)
   20180605 215652 worker: MPD output 1 ALSA default (on)
   20180605 215652 worker: MPD output 2 ALSA crossfeed (off)
   20180605 215652 worker: MPD output 3 ALSA parametric eq (off)
   20180605 215652 worker: MPD output 4 ALSA graphic eq (off)
   20180605 215652 worker: MPD output 5 ALSA bluetooth (off)
   20180605 215652 worker: MPD crossfade (off)
   20180605 215652 worker: (/usr/local/bin/shairport-sync -a "Moode Airplay" -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh -- -d hw:0 -c "Digital" > /dev/null 2>&1 &)
   20180605 215652 worker: Airplay receiver started
   20180605 215652 worker: Airplay volume mgt (auto)
   20180605 215652 worker: - Last
   20180605 215652 worker: USB sources (none attached)
   20180605 215652 worker: NAS sources (none configured)
   20180605 215652 worker: Volume level (87) restored
   20180605 215652 readMpdResponse(): reading response
   20180605 215652 readMpdResponse(): success $str=(OK)
   20180605 215652 readMpdResponse(): success $resp[0]=(OK)
   20180605 215652 worker: Maintenance interval (21600)
   20180605 215652 worker: Watchdog started
   20180605 215652 worker: Ready
   20180605 215653 engine-mpd: Connect
   20180605 215653 engine-mpd: Session loaded
   20180605 215653 engine-mpd: Open socket
   20180605 215653 readMpdResponse(): reading response
   20180605 215653 readMpdResponse(): success $str=(OK MPD 0.20.0)
   20180605 215653 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
   20180605 215653 engine-mpd: Get initial status
   20180605 215653 readMpdResponse(): reading response
   20180605 215653 readMpdResponse(): success $str=(OK)
   20180605 215653 readMpdResponse(): success $resp[0]=(volume: 87)
   20180605 215653 engine-mpd: UI state=(reconnect), MPD state=(stop)
   20180605 215653 engine-mpd: Generating enhanced metadata
   20180605 215653 readMpdResponse(): reading response
   20180605 215653 readMpdResponse(): success $str=(OK)
   20180605 215653 readMpdResponse(): success $resp[0]=(file: http://icy1.abacast.com:80/kplu-jazz24aac-64
)
   20180605 215653 enhanceMetadata(): Radio station
   20180605 215653 engine-mpd: Metadata returned to client: Size=(29)
   20180605 215653 engine-mpd: Connect
   20180605 215653 engine-mpd: Session loaded
   20180605 215653 engine-mpd: Open socket
   20180605 215653 readMpdResponse(): reading response
   20180605 215653 readMpdResponse(): success $str=(OK MPD 0.20.0)
   20180605 215653 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
   20180605 215653 engine-mpd: Get initial status
   20180605 215653 readMpdResponse(): reading response
   20180605 215653 readMpdResponse(): success $str=(OK)
   20180605 215653 readMpdResponse(): success $resp[0]=(volume: 87)
   20180605 215653 engine-mpd: UI state=(stop), MPD state=(stop)
   20180605 215653 engine-mpd: Idle
   20180605 215653 engine-mpd: Wait for idle timeout
   20180605 215653 readMpdResponse(): reading response
   20180605 220012 waitWorker(): Start (net-config, w_active=1)
   20180605 220012 worker: Job netcfg
   20180605 220013 waitWorker(): Wait  (1)
   20180605 220013 waitWorker(): End   (net-config, w_active=0)
   20180605 220015 engine-mpd: Connect
   20180605 220015 engine-mpd: Session loaded
   20180605 220015 engine-mpd: Open socket
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK MPD 0.20.0)
   20180605 220015 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
   20180605 220015 engine-mpd: Get initial status
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK)
   20180605 220015 readMpdResponse(): success $resp[0]=(volume: 87)
   20180605 220015 engine-mpd: UI state=(undefined), MPD state=(stop)
   20180605 220015 engine-mpd: Generating enhanced metadata
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK)
   20180605 220015 readMpdResponse(): success $resp[0]=(file: http://icy1.abacast.com:80/kplu-jazz24aac-64)
   20180605 220015 enhanceMetadata(): Radio station
   20180605 220015 engine-mpd: Metadata returned to client: Size=(29)
   20180605 220015 engine-mpd: Connect
   20180605 220015 engine-mpd: Session loaded
   20180605 220015 engine-mpd: Open socket
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK MPD 0.20.0)
   20180605 220015 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
   20180605 220015 engine-mpd: Get initial status
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK)
   20180605 220015 readMpdResponse(): success $resp[0]=(volume: 87)
   20180605 220015 engine-mpd: UI state=(stop), MPD state=(stop)
   20180605 220015 engine-mpd: Idle
   20180605 220015 engine-mpd: Wait for idle timeout
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): reading response
   20180605 220015 readMpdResponse(): success $str=(OK)
   20180605 220015 readMpdResponse(): success $resp[0]=(file: http://listen.sub.fm/hi/;&type=mp3)





Will cont to troubleshoot but running out of ideas [Image: sad.png]

thank you
Reply
#2
(06-06-2018, 05:22 AM)tracks Wrote: Eth0 is working good, and connected

Currently AP-Mode feature is only active if LAN is disconnected.

The situation has been described here.
Reply
#3
(06-06-2018, 05:22 AM)tracks Wrote: Hi

Would anyone have some info to get a USB WIFI network detected?  
Basically wlan0 is not in the network interface undifined for some reason , although the device is present. 
Also i made sure the Access Point is not left blank,, added the SSID info
Eth0 is working good, and connected
Im pretty sure it has to be a simple step missed , my first time using Moode.
I have put as much information sorry its a bit long thread.

...

Will cont to troubleshoot but running out of ideas [Image: sad.png]

thank you

@tracks 

This sounds similar to the problem reported by @agaufres

By default during its startup Raspbian now blocks the WiFi (via rfkill) if it finds the country code hasn't been set. The moOde configuration process undoes that and sets the country code to "US". However, @agaufres reported that his WiFi was blocked with a similar moOde report of the missing wlan interface. He is in Switzerland ("CH") and I infer you are in Sweden ("SE"). It isn't clear to me how the country code could be the root cause but I've repeated built and configured moOde in the US without incident.

What is the output you get when you run rfkill? If you see something like the following

Code:
pi@moode:~ $ sudo rfkill list
0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

then try unblocking it 

Code:
pi@moode:~ $ sudo rfkill unblock wlan


and check again for the wlan interface

Let us know if this works for you. If it does, then we need to revisit the way moOde initializes WiFi.

Regards,
Kent
Reply
#4
(06-06-2018, 05:22 AM)tracks Wrote: Hi

Would anyone have some info to get a USB WIFI network detected?  
Basically wlan0 is not in the network interface undifined for some reason , although the device is present. 
Also i made sure the Access Point is not left blank,, added the SSID info
Eth0 is working good, and connected
Im pretty sure it has to be a simple step missed , my first time using Moode.
I have put as much information sorry its a bit long thread.

cat  /etc/wpa_supplicant/wpa_supplicant.conf
#########################################
# This file is automatically generated by
# the player Network configuration page.
#########################################

country=SE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="MYSSID"
scan_ssid=1

}

Moode system log::
20180605 215648 worker: File check ok
   20180605 215648 worker: - Network
   20180605 215648 worker: eth0 exists
   20180605 215649 worker: eth0 (10.50.1.106)
   20180605 215649 worker: wlan0 does not exist
   20180605 215649 worker: - Audio
   20180605 215649 worker: ALSA outputs unmuted
   20180605 215649 worker: Audio out (I2S audio device)
   20180605 215649 worker: Audio dev (Allo Boss DAC)
   20180605 215649 worker: ALSA mixer name (Digital)
   20180605 215649 worker: MPD volume control (software)
   20180605 215649 worker: Hdwr volume controller exists
   20180605 215650 worker: Chip options (Burr Brown PCM5122)
   20180605 215650 worker: - Services
   20180605 215652 worker: MPD started
   20180605 215652 worker: MPD scheduler policy (time-share)
   20180605 215652 worker: Configure MPD outputs
.
.
.

The message "wlan0 adapter does not exist" in moode log even though an adapter is physically present suggests a broken Build.

Which method did you select when you built moode 4.1?

-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#5
(06-06-2018, 11:53 AM)TheOldPresbyope Wrote:
(06-06-2018, 05:22 AM)tracks Wrote: Hi

Would anyone have some info to get a USB WIFI network detected?  
Basically wlan0 is not in the network interface undifined for some reason , although the device is present. 
Also i made sure the Access Point is not left blank,, added the SSID info
Eth0 is working good, and connected
Im pretty sure it has to be a simple step missed , my first time using Moode.
I have put as much information sorry its a bit long thread.

...

Will cont to troubleshoot but running out of ideas [Image: sad.png]

thank you

@tracks 

This sounds similar to the problem reported by @agaufres

By default during its startup Raspbian now blocks the WiFi (via rfkill) if it finds the country code hasn't been set. The moOde configuration process undoes that and sets the country code to "US". However, @agaufres reported that his WiFi was blocked with a similar moOde report of the missing wlan interface. He is in Switzerland ("CH") and I infer you are in Sweden ("SE"). It isn't clear to me how the country code could be the root cause but I've repeated built and configured moOde in the US without incident.

What is the output you get when you run rfkill? If you see something like the following

Code:
pi@moode:~ $ sudo rfkill list
0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

then try unblocking it 

Code:
pi@moode:~ $ sudo rfkill unblock wlan


and check again for the wlan interface

Let us know if this works for you. If it does, then we need to revisit the way moOde initializes WiFi.

Regards,
Kent

Thanks for the suggestion Kent, but there is no rfkill process in my case,, i think its because the wlan0 is not present at all 
I think i need to try a new re-install with the USB WIFI attached, i answered Tim with that.

pi@moode:~ $ sudo rfkill list
pi@moode:~ $ sudo rfkill list
pi@moode:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.50.1.106  netmask 255.255.255.0  broadcast 10.50.1.255
        inet6 fe80::54:d5a9:fd5b:be4a  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:1a:85:90  txqueuelen 1000  (Ethernet)
        RX packets 68006  bytes 17061594 (16.2 MiB)
        RX errors 0  dropped 34  overruns 0  frame 0
        TX packets 4739  bytes 2424331 (2.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 519  bytes 41463 (40.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 519  bytes 41463 (40.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
\regards
Reply
#6
(06-07-2018, 05:02 AM)tracks Wrote:
(06-06-2018, 11:53 AM)TheOldPresbyope Wrote:
(06-06-2018, 05:22 AM)tracks Wrote: Hi

Would anyone have some info to get a USB WIFI network detected?  
Basically wlan0 is not in the network interface undifined for some reason , although the device is present. 
Also i made sure the Access Point is not left blank,, added the SSID info
Eth0 is working good, and connected
Im pretty sure it has to be a simple step missed , my first time using Moode.
I have put as much information sorry its a bit long thread.

...

Will cont to troubleshoot but running out of ideas [Image: sad.png]

thank you

@tracks 

This sounds similar to the problem reported by @agaufres

By default during its startup Raspbian now blocks the WiFi (via rfkill) if it finds the country code hasn't been set. The moOde configuration process undoes that and sets the country code to "US". However, @agaufres reported that his WiFi was blocked with a similar moOde report of the missing wlan interface. He is in Switzerland ("CH") and I infer you are in Sweden ("SE"). It isn't clear to me how the country code could be the root cause but I've repeated built and configured moOde in the US without incident.

What is the output you get when you run rfkill? If you see something like the following

Code:
pi@moode:~ $ sudo rfkill list
0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

then try unblocking it 

Code:
pi@moode:~ $ sudo rfkill unblock wlan


and check again for the wlan interface

Let us know if this works for you. If it does, then we need to revisit the way moOde initializes WiFi.

Regards,
Kent

Thanks for the suggestion Kent, but there is no rfkill process in my case,, i think its because the wlan0 is not present at all 
I think i need to try a new re-install with the USB WIFI attached, i answered Tim with that.

pi@moode:~ $ sudo rfkill list
pi@moode:~ $ sudo rfkill list
pi@moode:~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.50.1.106  netmask 255.255.255.0  broadcast 10.50.1.255
        inet6 fe80::54:d5a9:fd5b:be4a  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:1a:85:90  txqueuelen 1000  (Ethernet)
        RX packets 68006  bytes 17061594 (16.2 MiB)
        RX errors 0  dropped 34  overruns 0  frame 0
        TX packets 4739  bytes 2424331 (2.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 519  bytes 41463 (40.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 519  bytes 41463 (40.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
\regards

Hi,

Found problem,, documented it for the forum.

It turns out that the USB Wifi from Linksys does not have a linux driver , the way to found out is from the syslog as follows:

Jun  5 14:01:44 moode kernel: [    2.623406] usb 1-1.5: New USB device found, idVendor=13b1, idProduct=0042
Jun  5 14:01:44 moode kernel: [    2.638528] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun  5 14:01:44 moode kernel: [    2.653897] usb 1-1.5: Product: USBWLAN
Jun  5 14:01:44 moode kernel: [    2.665690] usb 1-1.5: Manufacturer: Qualcomm Atheros
Jun  5 14:01:44 moode kernel: [    2.678787] usb 1-1.5: SerialNumber: 12345678
Jun  5 14:01:44 moode kernel: [    3.212926] NET: Registered protocol family 10

Note that Qualcom Atheros is not the driver for Linksys and its bogus, 

The specs from USB LINKSYS has no drivers for Linux,, so i have to be carefull when buying those USB WIFI to double check compatibility..

Case close ordered a new one.. my favorit ASUS..

cheers
/hubert
Reply
#7
Hi Hubert,

I was going to post regarding possibly no driver support for the Linksys adapter but you've already determined that. One thing to be aware of is that even if manufacturer specifies "Linux driver available" in some few cases the driver is available but was never submitted to Linusx kernel. You would have to compile it into the kernel by hand :-0

Would you mind changing [PROBLEM] to [SOLVED] in you OP?

Thx,
-Tim
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#8
(06-08-2018, 10:42 PM)Tim Curtis Wrote: Hi Hubert,

I was going to post regarding possibly no driver support for the Linksys adapter but you've already determined that. One thing to be aware of is that even if manufacturer specifies "Linux driver available" in some few cases the driver is available but was never submitted to Linusx kernel. You would have to compile it into the kernel by hand :-0

Would you mind changing [PROBLEM] to [SOLVED] in you OP?

Thx,
-Tim

Hi Tim

Thanks for your support, i will change it to Solved,, im very new to this forum was looking for how to do this last time

cheers
Reply


Forum Jump: