Open cguess opened 11 years ago
When you re-run byzantium_configd.py, could you capture its output to files and paste them into comments to this ticket?
byzantium_configd.py 1>/tmp/stdout.log 2>/tmp/stderr.log
Also, what wireless adapter are you using on your end? Make and model would be helpful, as would the output of lsusb -v
.
Did it work before you ran the ByzPi setup procedure, or were you using the Ethernet interface to install everything?
This may have been related to the wireless firmware not being installed.
On Sat, Jan 18, 2014 at 7:44 PM, The Doctor notifications@github.comwrote:
When you re-run byzantium_configd.py, could you capture its output to files and paste them into comments to this ticket?
byzantium_configd.py 1>/tmp/stdout.log 2>/tmp/stderr.log
Also, what wireless adapter are you using on your end? Make and model would be helpful, as would the output of lsusb -v.
Did it work before you ran the ByzPi setup procedure, or were you using the Ethernet interface to install everything?
— Reply to this email directly or view it on GitHubhttps://github.com/Byzantium/ByzPi/issues/23#issuecomment-32697853 .
I haven't had a chance to recreate this yet, but unless the Byz software uninstalls drivers, this wouldn't be a factor. The standard Rasbian install works with the dongle before Byz is installed.
-Christopher Guess http://www.tryandguess.com cguess@gmail.com +1 262.893.1037
On Mon, Jan 20, 2014 at 3:15 PM, Ben Mendis notifications@github.comwrote:
This may have been related to the wireless firmware not being installed.
On Sat, Jan 18, 2014 at 7:44 PM, The Doctor notifications@github.comwrote:
When you re-run byzantium_configd.py, could you capture its output to files and paste them into comments to this ticket?
byzantium_configd.py 1>/tmp/stdout.log 2>/tmp/stderr.log
Also, what wireless adapter are you using on your end? Make and model would be helpful, as would the output of lsusb -v.
Did it work before you ran the ByzPi setup procedure, or were you using the Ethernet interface to install everything?
— Reply to this email directly or view it on GitHub< https://github.com/Byzantium/ByzPi/issues/23#issuecomment-32697853> .
— Reply to this email directly or view it on GitHubhttps://github.com/Byzantium/ByzPi/issues/23#issuecomment-32793116 .
Can you capture the output of dmesg
in addition to the output from byzantium_configd.py? I have a feeling that some answers are going to be in there.
I'm having the same issue. Fresh Raspbian Jessie install followed by the install.sh. Ralink RT5370 (which is listed on the HCL as working) and it was working prior to the ByzPi setup.
everything in byzantium_config.py errors out as "Set failed on device wlan0 ; operation not permitted"
A couple more data points.
I have the same results as above with 2 different USB wifi adapters. Ralink RT2870/3070 and Ralink RT2500.
I've taken a fresh Rasbian installation, working with the RTL8188CUS chipset and installed the Byzantium builds as described in the wiki. However, after Puppet does its thing, wlan0 is no longer anywhere to be found. Attempting to run the byzantium_configd.py script fails out since it can't find anything to configure.
Thank you for the work you're doing and thanks ahead of time for any help you guys can provide.