starbasessd
commented
4 years ago Do you have a Linux PC that you can look at the logs? Which model specifically of the tp-link? Can you do a dmesg | grep usb to get the discovery from the Raspbian, to see what driver is being used, please?
On Fri, Apr 3, 2020 at 5:03 PM thecheeseontoast notifications@github.com wrote:
Preliminary Docs
I confirm that I have read the CONTRIBUTING https://github.com/ccrisan/motioneyeos/blob/master/.github/CONTRIBUTING.md guide before opening this issue.
I confirm that I have read the FAQ https://github.com/ccrisan/motioneyeos/wiki/FAQ before opening this issue. motionEyeOS Version
I am running motionEyeOS version: 20190911 Board Model
I am using the following board/model: Pi Zero (not W) Camera
I am using the following type of camera: can't even boot, let alone worry about the camera
My camera model is: " Network Connection
My motionEyeOS unit is connected to the network via: Ethernet, tp-link adapter Peripherals
I am using the following peripherals that I consider relevant to this issue:
- USB-ethernet adapter
##################
Pi is stuck in bootloop as the OS fails to find a network. Testing on raspbian, the network is found instantly with no set-up. Only on motioneyeos does it fail to find anything. As such, I can't get past the boot. Adapter works fine with raspbian, my linux machine etc. Status light indicates it has connection as motioneyeos boots, yet the os clearly can't find anything.
Any suggestions on steps I should take?
— 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/2343, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHNFB4ZCBOY3U47KNJTRKZFJRANCNFSM4L4OCCAA .
-- 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?
thecheeseontoast
ccrisan
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: 20190911
Board Model
I am using the following board/model: Pi Zero (not W)
Camera
I am using the following type of camera: can't even boot, let alone worry about the camera
My camera model is: "
Network Connection
My motionEyeOS unit is connected to the network via: Ethernet, tp-link adapter
Peripherals
I am using the following peripherals that I consider relevant to this issue:
##################
Pi is stuck in bootloop as the OS fails to find a network. Testing on raspbian, the network is found instantly with no set-up. Only on motioneyeos does it fail to find anything. As such, I can't get past the boot. Adapter works fine with raspbian, my linux machine etc. Status light indicates it has connection as motioneyeos boots, yet the os clearly can't find anything.
Any suggestions on steps I should take?