Open dzianisv opened 4 years ago
I have three wifi devices with the same chipset. Unfortunately brcmfmac (build-in RPI 3 wifi) does not work either. It would be nice to have some idea what kind of wifi keys work, because most I can find seem to be realtek ones.
If it works in a current Raspbian image, it should work in motionEyeOS. I have a bunch of different ones rtl8192cu Edimax rtl8712u Asus N10 BCM20702A0 Plugable (BT & WiFi) rtl8192cu Xerox Wireles N rt2x00 RALink Long range rtl8192cu LB Link long range All work with both Raspbian and motionEyeOS. Does your OTG cable or hub work with other devices?
On Thu, Apr 2, 2020 at 10:41 AM micmon notifications@github.com wrote:
I have three wifi devices with the same chipset. Unfortunately brcmfmac (build-in RPI 3 wifi) does not work either. It would be nice to have some idea what kind of wifi keys work, because most I can find seem to be realtek ones.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2275#issuecomment-607887413, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHM4OSU3A25PRHD4T2LRKSPYFANCNFSM4KO2HACA .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Got my r8188eu working by ssh'ing in when connected via cable and doing the following:
iwconfig wlan0 mode Managed iwconfig wlan0 essid myssid service wifi restart dhclient wlan0
Now the wifi even connects fine after a reboot. Maybe there is something that needs to be added to the setup or init scripts?
Spoke too soon, now it fails again....
Problem solved: SSIDs are case-sensitive after all :-)
Yep. You can sometimes get away with it in Windows, but not in Linux or MacOS... If you set up your wpa_supplicant.conf file ahead of time, and copy to the /boot partition when imaging, you shouldn't have any issues.
On Thu, Apr 2, 2020 at 12:06 PM micmon notifications@github.com wrote:
Problem solved: SSIDs are case-sensitive after all :-)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2275#issuecomment-607938750, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHI6ATBJVP5CN5NCN6DRKSZYBANCNFSM4KO2HACA .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
It seems that r8188eu is not included into the distro.
Preliminary Docs
I confirm that I have read the CONTRIBUTING guide before opening this issue.
I confirm that I have read the FAQ before opening this issue.
motionEyeOS Version
I am running motionEyeOS version: motioneyeos-orangepione-20190911
Board Model
I am using the following board/model: Orange Pi PC One
Camera
I am using the following type of camera: V4L2
Network Connection
My motionEyeOS unit is connected to the network via: ethernet
Peripherals
I am using the following peripherals that I consider relevant to this issue:
USB WiFi adapter based on Relatek 8188.
Bus 003 Device 002: ID 0bda:8179
Linux module isr8188eu
Log Files
I consider the following log files relevant to this issue: