I'm trying to create a wi-fi hostspot using a beaglebone black rev-C and DWA-131 nano wi-if adapter.
I followed this article to install the driver:
http://www.linux-hardware-guide.com/2013-11-16-d-link-dwa-131-n300-usb-wifi-adapter
And this project do setup the hostapd: https://github.com/jekader/hostapd-rtl
But when I try to start I'm getting the following error:
Configuration file: /etc/hostapd/hostapd.conf
drv->ifindex=4
l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
no br0 interface , let l2_sock_recv==l2_sock_xmit=0x0x51648
ioctl[SIOCSIWMODE]: Operation not supported
Could not set interface to mode(3)!
Could not set interface to master mode!
rtl871xdrv driver initialization failed.
rmdir[ctrl_interface]: No such file or directory
My hostapd.conf is:
interface=usb0
driver=rtl871xdrv
bridge=br0
ssid=NETWORK-NAME
channel=1
wmm_enabled=0
wpa=1
wpa_passphrase=NETWORK-PASSWORD
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
auth_algs=1
macaddr_acl=0
Hostapt version? Driver's name or config?
ps: I'm not confortable because my network interface for the wi-fi is usb0 instead of wlan0. Is a driver issue?
I had same compilation issues. Following is working very well, you get the source directly from git.
sudo apt-get install git build-essential
git clone https://github.com/Mange/rtl8192eu-linux-driver.git
cd rtl8192eu-linux-driver
make
sudo make install
Related
It seems that I'm facing a delemma. I need to run kvaser_interface ROS1 (noetic, 1.15.14) node. I'm using this repo: https://github.com/astuff/kvaser_interface
I follow this link to install kvaser CAN/USB driver on my ubuntu 20.04.4. If I don't install CANlib or linuxcan, I can have my CAN network working (can0 is listed, candump and cansend works). But kvaser_interface needs a library from linuxcan, hence gives me error:
... kvaser_can_bridge: error while loading shared libraries: libcanlib.so.1: cannot open shared object file: No such file or directory
Apparently kvaser_interface node requires CANlib. So I installed linuxcan and CANlib using:
sudo make install
kvaser_interface runs without a problem. But can0 isn't working anymore.
ip link
doesn't show can0. Also
sudo ip link set can0 type can bitrate 500000
gives
Cannot find device "can0"
This is because linuxcan blacklists socketCAN. It seems that I'm facing a delimma. Also I'm not clear what role CANlib is playing here. Any suggests will help. Thank you.
I have not tested this yet, but you can go into the
/etc/modprobe.d/kvaser.conf
and sudo edit the file to delete the blacklisted modules:
https://askubuntu.com/questions/110341/how-to-blacklist-kernel-modules
I'm trying to install ROS on my VMware fusion 12, but after updating the bash file as per the installation document, I get an error when I enter roscore in the terminal. The error seems to be that my VMware cannot ping itself. It also affected me using openCv. It offers a solution which asks me to ping an IP address, however when I do this I get another error which I also included in this question. Thanks for your help!
Here is the error
This causes because of wrong configuration of ros parameters .
Check your ros parameter configuration on the VM
Keep in mind that roscore and all other ros commands run without root permission
### Configuring the parameter on VM ####
export YOUR_VM_IP=192.168.7.2
#setting ROS_MASTER_URI as VM's_ip ####
export ROS_MASTER_URI=http://192.168.7.2:11311
If this not work manually add above the ROS parameters lines on ~/.bashrc executing the following commands
sudo vim ~/.bashrc
sudo source ~/.bashrc
sudo source ~/.profile
Also check my answer on Robotics.Stackexchange for accessing master/remote ros notes correctly.
How to call remote ROS node on mobile robot through laptop using wifi?
Also try this link Setting up ROS on a virtual machine
Hope this will somewhat help you !
i'm trying to make fake webcam using v4l2loopback on a docker container inside gcp instance.
i'm using debian:stretch with 4.9.0-9-amd64 kernel
so far, these are steps that i tried to compile the v4l2loopback:
`apt install linux-headers-$(uname -r)` to install proper header
`apt-get install kmod` and `apt-get install make` so i can use `make` and `depmod` feature
`apt-get install aufs-dkms aufs-tools aufs-dev` to get the `modules.builtin.bin` file
after steps above, i cloned the v4l2loopback repo, run make && sudo make install command, and finally depmod -a command. But when i run depmod -a, i got this warning:
depmod: WARNING: could not open /lib/modules/4.9.0-9-amd64/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/4.9.0-9-amd64/modules.builtin: No such file or directory
when i check it manually, there are no modules.order and modules.builtin inside the /lib/modules/4.9.0-9-amd64 directory.
so when i tried to load the v4l2loopback module using modprobe v4l2loopback, it gives me error like this:
modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.9.0-9-amd64/modules.builtin.bin'
modprobe: ERROR: could not insert 'v4l2loopback': Operation not permitted
how can i fix this? or how can i compile the v4l2loopback properly on my environment?
In my case, I realized that it is only possible to load the module via insmod command instead of modprobe and you would be ready to use. Here you can find an explanation about the differences between these methods.
Example: sudo insmod PATH/TO/THE/FILE/v4l2loopback.ko devices=2 card_label="camera1","camera2" exclusive_caps=1,1
I am using mosquitto as one of my project tool. After i successfully compile (make binary) mosquitto via source code and try to run mosquitto_sub/pub, its shows that
./mosquitto_sub: /usr/lib/i386-linux-gnu/libmosquitto.so.1: version `MOSQ_1.5' not found (required by ./mosquitto_sub)
while Mosquitto and Mosquitto_psswd is able is run without any problem. Besides, my mosquitto version is 1.5.
I have no idea about this problem.
Any Help appreciated .
It sounds like you have an earlier version of mosquitto installed and it's libraries are on the system path.
Make sure you have uninstalled any earlier versions of mosquitto installed on the machine.
Also make sure you have run make install as root in your build directory to copy the libraries to the correct locations
I had a similar issue building on rpi model B+ using GNU make 4.2.1 and cc (Raspbian 8.3.0-6+rpi1) 8.3.0
Error reported: ./mosquitto_sub: /usr/lib/i386-linux-gnu/libmosquitto.so.1: version `MOSQ_1.6' not found (required by ./mosquitto_sub)
Note: I left the existing distribution in place so that I could leverage off the systemd mosquitto.service that gets installed with the debian packages mosquitto and mosquitto-clients.
Resolution:
mkdir proj
git clone https://github.com/eclipse/mosquitto.conf
cd mosquitto
# my build failed on master branch, so I picked a tag that worked for me
git checkout -b 1.6.9 tags/1.6.9
make WITH_WEBSOCKETS=yes WITH_DOCS=yes WITH_SRV=yes
# overwrite the existing binaries
sudo make install
sudo ldconfig
# verify that the newly installed binaries have overwritten the originals.
mosquitto --help|grep -w 'mosquitto version'
mosquitto_pub --help|grep -w 'mosquitto_pub version'
mosquitto_sub --help|grep -w 'mosquitto_sub version'
currently I am using Fedora 19 (since a few days) but the setup of Wi-Fi let me going crazy. I'm using the Realtek RTL 8192CU Wi-Fi-adapter usb-dongle. Fedora recognizes my network, I enter the right password and using the correct encryption option, but the system still asking for the password.
Does anyone has a solution for my problem?
Thanks for your help.
Run yum update to make sure your system is up to date. Run yum install #'Developer Tools' if you have not previously installed the GNU build tools.
Download the latest drivers from Realtek (Version 3.4.4_4749)
Download this patch.
Extract the driver. In the directory "driver," there is another zip, extract that as well. Finally put the patch in that folder.
CD into the zip you extracted from the command line and type:
patch -p1 < use_kthread_run.patch
Type make, followed by make install. Finally you need to run modprobe 8192cu. You may also want to blacklist the previous driver.
Check /var/log/messages for NetworkManager messages. You should see what is failing there.