Good idea. I’ll try it tomorrow. Do I need a driver for Windows?
I’ll try anything. Can you tell me how to do this?
Again, I appreciate the help. Thank you.
Win10 already has the driver build in
Hello again. I’ve pursued fzinken and Sam’s suggestions and here is what I’ve found (Bottom line: dongle is still not working with my setup):
I unplugged the ethernet cable from my desktop running Windows 10 and plugged the OSMC dongle into a vacant USB port. Nothing. So I unplugged it and plugged it into a different USB port. It connected and I was able to connect to my 5G network with no problem. The dongle works with Windows 10.
I did my best to figure out what this means. I hope I got it right. Here is a log of what I did this morning:
Onboard wifi disabled via dtoverlay=sdhost
Rebooted Pi
Disconnected from wifi via OSMC > Network
Disabled wifi via OSMC > Network
Enabled ethernet via OSMC > Network
Plugged in ethernet cable
SSH’d into Pi via ethernet IP
Entered routing command suggested by Sam: sudo route add default gw 192.168.1.254 dev wlan0
Got reply “SIOCADDRT: No such device”. I guess that makes sense, since I disabled it wifi.
So, plug in dongle and enable wifi, but don’t log in to an SSID yet
Enter routing command (above)
Got response “SIOCADDRT: Network is unreachable”. So, evidently, I have to be logged in to an SSID in order to enter the route command?
So, disable ethernet, log into 2.4G, and try again
On log in to 2.4G, “Connection failed” message from OSMC
Backed out of wireless screen to My OSMC and unplugged ethernet cable
Back into wireless, connect to 2.4G and apply. OSMC reports “connected”
Log into Pi using this IP address. Connection timed out.
Backed out to OSMC home and selected “Weather”. Viewed weather, so assume connected to internet
Tried logging in SSH again. Again, connection timed out
Back to Pi, Power > Exit, then esc to get command line
Logged directly into Pi, added routing line (above), got message “File exists”. Huh?
Then did sudo nano /etc/rc.local and added the routing line without the sudo; i.e., added “route add default gw 192.168.1.254 dev wlan0”
Should I have included “Sudo” in the rc.local file?
Rebooted Pi
Disable ethernet, unplug ethernet cable
Enable wifi, attempt to connect to 5G
Upon selecting “Apply”, status “No Internet”
My OSMC > Network > Wireless reports default gateway “blank” huh?
Based on these results, it seems like the OSMC dongle or its driver is not playing well with my router. I will see if AT&T has any ideas on how to handle this, but I’m not hopeful. I’m also not interested in messing up all the other connections to that router that are working just fine. Do you folks have any ideas on what questions to pose to AT&T when I go that route?
Also, before I head over to AT&T, is there anything else I should be trying?
Again, thank you very much.
There’s a lot covered in your last post, but I’ll focus on one point for now.
Adding the “route add” line to /etc/rc.local isn’t working because the command is executed before the WiFi network has been brought up. I find exactly the same issue. A “hacky” solution is to place a sleep command before the route add command to give it time to start. Probably 5 seconds will be sufficient, so you’d have two lines:
sleep 5
route add default gw 192.168.1.254 dev wlan0
(And yes, you don’t need sudo since /etc/rc.local is run under the root user. And remember to place those lines before the exit 0 line.)
Thank you, dillthedog.
Here’s what I did in response to your suggestion:
Added sleep 10 for good measure
Yes, added lines before “exit 0”
Back to Pi
Disable wired, unplug ethernet cable
Plug in dongle
Enable wireless, select 5G network
Apply, note status “No Internet”
Reboot
My OSMC > Network > Wireless Status “No Internet”, Default gateway blank
Attempt to set default gateway in My OSMC > Network > Wireless had no effect
Still “No internet”
Anything else to try?
Thanks again to all.
Could you please confirm (or otherwise) one point. Did you sanitize any of the data you’ve posted above to, for example, remove MAC addresses and/or the WiFi passphrase(s)?
It might be worth trying a different approach, using connmanctl. Please list the full output from point 2 and 3 below (format with </>).
1 Attach a network cable and reboot. While it’s rebooting, remove the dongle then SSH to the cable IP address.
2 Run the following:
route -n
connmanctl
config wifi_000000000000_3239436f766552642d3547_managed_psk --remove
config wifi_000000000000_3239436f76655264_managed_psk --remove
(The above assumes that the service names haven’t been sanitized.)
3 Plug in the dongle, wait a few seconds, then (still in connmanctl), run:
enable wifi
scan wifi
services
agent on
connect wifi_000000000000_3239436f766552642d3547_managed_psk
*Enter passphrase and wait for connected message*
services wifi_000000000000_3239436f766552642d3547_managed_psk
quit
route -n
4 Finally, run grab-logs -A
Thanks again for hanging with me!
I didn’t get far. Here’s what happened:
osmc@RPi3OSMC1:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
osmc@RPi3OSMC1:~$ connmanctl
connmanctl> config wifi_000000000000_3239436f766552642d3547_managed_psk --remove
Error wifi_000000000000_3239436f766552642d3547_managed_psk: Method "Remove" with signature "" on interface "net.connman.Service" doesn't exist
connmanctl> config wifi_000000000000_3239436f76655264_managed_psk --remove
Error wifi_000000000000_3239436f76655264_managed_psk: Method "Remove" with signature "" on interface "net.connman.Service" doesn't exist
connmanctl>
Thanks again for your help.
Looks like the services aren’t there., so perhaps the remove step is redundant.
What’s the output from running connmanctl services?
osmc@RPi3OSMC1:~$ connmanctl services
*AO Wired ethernet_b827eb83727e_cable
osmc@RPi3OSMC1:~$
I guess the wireless services aren’t there because the dongle is not plugged in?
Yep. Now plug in the dongle and proceed to step 3.
Hi again,
Here is my session. As you can see, grab-logs -A failed. Not sure why. Maybe because I just ran it a few minutes ago?
osmc@RPi3OSMC1:~$ connmanctl
Error getting VPN connections: Unit connman-vpn.service not found.connmanctl>
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
*AO Wired ethernet_b827eb83727e_cable
*A 29CoveRd-5G wifi_000000000000_3239436f766552642d3547_managed_psk
29CoveRd wifi_000000000000_3239436f76655264_managed_psk
wifi_000000000000_hidden_managed_psk
manofsteel wifi_000000000000_6d616e6f66737465656c_managed_psk
Disneyland wifi_000000000000_4469736e65796c616e64_managed_psk
ATTIz4Y9MS wifi_000000000000_415454497a3459394d53_managed_psk
Disneyland-Guest wifi_000000000000_4469736e65796c616e642d4775657374_mana ged_psk
ATTPUxPMkI wifi_000000000000_415454505578504d6b49_managed_psk
DIRECT-1C-HP ENVY 5540 series wifi_000000000000_4449524543542d31432d48502045 4e5659203535343020736572696573_managed_psk
Disney World wifi_000000000000_4469736e657920576f726c64_managed_psk
thedarkknight wifi_000000000000_7468656461726b6b6e69676874_managed_ps k
Schmidt_Casa wifi_000000000000_5363686d6964745f43617361_managed_psk
NewThermostat_741FA5 wifi_000000000000_4e6577546865726d6f737461745f373431464 135_managed_none
connmanctl> agent on
Agent registered
connmanctl> connect wifi_000000000000_3239436f766552642d3547_managed_psk
Connected wifi_000000000000_3239436f766552642d3547_managed_psk
connmanctl> services wifi_000000000000_3239436f766552642d3547_managed_psk
/net/connman/service/wifi_000000000000_3239436f766552642d3547_managed_psk
Type = wifi
Security = [ psk, wps ]
State = ready
Strength = 49
Favorite = True
Immutable = False
AutoConnect = True
Name = 29CoveRd-5G
Ethernet = [ Method=auto, Interface=wlan0, Address=00:00:00:00:00:00, MTU=1500 ]
IPv4 = [ Method=dhcp, Address=192.168.1.94, Netmask=255.255.255.0 ]
IPv4.Configuration = [ Method=dhcp ]
IPv6 = [ ]
IPv6.Configuration = [ Method=off ]
Nameservers = [ 192.168.1.254 ]
Nameservers.Configuration = [ ]
Timeservers = [ ]
Timeservers.Configuration = [ ]
Domains = [ attlocal.net ]
Domains.Configuration = [ ]
Proxy = [ Method=direct ]
Proxy.Configuration = [ ]
Provider = [ ]
connmanctl> quit
osmc@RPi3OSMC1:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
192.168.1.254 0.0.0.0 255.255.255.255 UH 0 0 0 wlan0
192.168.1.254 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
osmc@RPi3OSMC1:~$ grab-logs -A
Exception Details:
Traceback (most recent call last):
File "/usr/bin/grab-logs", line 798, in dispatch_logs
raise ValueError('Upload Returned Empty String')
ValueError: Upload Returned Empty String
Failed to upload log files, copying to /boot instead. (Unable to verify)
osmc@RPi3OSMC1:~$Try to SSH to IP address 192.168.1.94 from a separate terminal session. Let’s see if it’s really connected.
Nope. “Connection timed out” from puTTy.
How about ping 192.168.1.94?
Interestingly, I had quit the previous puTTY session and could no longer SSH into the Pi via the ethernet port, so I opened a command prompt from my Windows 7 PC and did a ping. This is what I got:
C:\Users\Ed's>ping 192.168.1.94
Pinging 192.168.1.94 with 32 bytes of data:
Request timed out.
Request timed out.
So, I guess it’s really not connected. (My router says it’s connected too.)
This is not what we expect to see. All the MAC addresses are zeroed out.
connmanctl> services
*AO Wired ethernet_b827eb83727e_cable
*A 29CoveRd-5G wifi_000000000000_3239436f766552642d3547_managed_psk
29CoveRd wifi_000000000000_3239436f76655264_managed_psk
wifi_000000000000_hidden_managed_psk
manofsteel wifi_000000000000_6d616e6f66737465656c_managed_psk
Disneyland wifi_000000000000_4469736e65796c616e64_managed_psk
ATTIz4Y9MS wifi_000000000000_415454497a3459394d53_managed_psk
Disneyland-Guest wifi_000000000000_4469736e65796c616e642d4775657374_managed_psk
ATTPUxPMkI wifi_000000000000_415454505578504d6b49_managed_psk
DIRECT-1C-HP ENVY 5540 series wifi_000000000000_4449524543542d31432d485020454e5659203535343020736572696573_managed_psk
Disney World wifi_000000000000_4469736e657920576f726c64_managed_psk
thedarkknight wifi_000000000000_7468656461726b6b6e69676874_managed_psk
Schmidt_Casa wifi_000000000000_5363686d6964745f43617361_managed_psk
NewThermostat_741FA5 wifi_000000000000_4e6577546865726d6f737461745f373431464135_managed_none
This shows that the problem is probably not with your router, since you’ve hoovered up all the neighbouring WiFi devices and they all show the same zeroed MAC address.
So on balance it suggests to me that it’s either a problem with your OSMC installation (are you using NOOBS?) or with the dongle itself.
The current installation was done using NOOBS, but I tried a fresh install without NOOBS last night and experienced exactly the same problems.
Sounds like I have a bad dongle then? (Recall that it did work fine with my Windows 10 machine.)
My instinct tells me it could be a driver issue too, but maybe that’s just part of the OSMC installation? Should I try a different version of OSMC?
Thanks again for all your help. I’m still hoping I can get this thing going!
Perhaps worth installing a vanilla version of OSMC.
Good point.
The version I installed and tried last night came directly from osmc.tv. I selected the most recent version. Is there another vanilla version of OSMC I should try instead?
Were there changes made to the dongle driver in a recent update of OSMC? If so, maybe I should try a version before such changes.
Regarding the MAC addresses, isn’t is standard for those to be hidden from public view; i.e., I guess I’d be surprised to see someone else’s MAC addresses showing up on my computer.
It’s beginning to sound like I’m stuck.