I recently installed Centos 7 and I have not been able to setup wifi. Whenever I am turning wifi on, I am getting below message :
Below is the output of /var/log/messages
Dec 6 22:07:54 [localhost] NetworkManager[4054]: <info> [1512578274.9743] manager: rfkill: WiFi hardware radio set enabled
Dec 6 22:07:54 [localhost] kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Dec 6 22:07:54 [localhost] kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Dec 6 22:07:55 [localhost] kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Dec 6 22:07:55 [localhost] kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
Dec 6 22:07:55 [localhost] NetworkManager[4054]: <info> [1512578275.2151] audit: op="radio-control" arg="wireless-enabled:1" pid=2071 uid=1000 result="success"
Dec 6 22:07:55 [localhost] kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Dec 6 22:07:55 [localhost] NetworkManager[4054]: <info> [1512578275.2157] manager: rfkill: WiFi now enabled by radio killswitch
Dec 6 22:07:55 [localhost] google-chrome.desktop: [2559:2665:1206/220755.949908:ERROR:connection_factory_impl.cc(386)] Failed to connect to MCS endpoint with error -106
I installed the latest version of the driver and it worked.
Strangely driver mentioned that was supposed to be compatible was not good enough
Related
After trying for quite a long time to create a udev rule to automatically mount a USB-Stick to a directory, I have to realize that I can't get any further without help.
Here is my udev-rule stored at /etc/udev/rules.d/60-usbspecialmount.rules
ACTION=="add", SUBSYSTEMS=="usb", KERNEL=="sd?", ATTRS{serial}=="3f980000.usb", RUN+="/bin/mount /dev/%k /media/securitycam
ACTION=="remove", SUBSYSTEMS=="usb", KERNEL=="sd?", RUN+="/bin/umount /dev/%k"
after restarting the udev service with:
sudo service udev restart
and plugging in the USB-Device, the SYSLOG-File says following:
Sep 13 05:47:17 raspberrypi systemd[1]: Stopping Rule-based Manager for Device Events and Files...
Sep 13 05:47:17 raspberrypi systemd[1]: systemd-udevd.service: Succeeded.
Sep 13 05:47:17 raspberrypi systemd[1]: Stopped Rule-based Manager for Device Events and Files.
Sep 13 05:47:17 raspberrypi systemd[1]: systemd-udevd.service: Consumed 1.424s CPU time.
Sep 13 05:47:17 raspberrypi systemd[1]: Starting Rule-based Manager for Device Events and Files...
Sep 13 05:47:17 raspberrypi systemd[1]: Started Rule-based Manager for Device Events and Files.
Sep 13 05:48:04 raspberrypi kernel: [ 6571.111154] usb 1-1.4: new high-speed USB device number 25 using dwc_otg
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242509] usb 1-1.4: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242543] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242563] usb 1-1.4: Product: Flash Disk
Sep 13 05:48:04 raspberrypi kernel: [ 6571.242581] usb 1-1.4: Manufacturer: USB
Sep 13 05:48:04 raspberrypi kernel: [ 6571.243643] usb-storage 1-1.4:1.0: USB Mass Storage device detected
Sep 13 05:48:04 raspberrypi kernel: [ 6571.244623] usb-storage 1-1.4:1.0: Quirks match for vid 090c pid 2000: 800000
Sep 13 05:48:04 raspberrypi kernel: [ 6571.244816] scsi host0: usb-storage 1-1.4:1.0
Sep 13 05:48:04 raspberrypi mtp-probe: checking bus 1, device 25: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Sep 13 05:48:04 raspberrypi mtp-probe: bus: 1, device: 25 was not an MTP device
Sep 13 05:48:04 raspberrypi mtp-probe: checking bus 1, device 25: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Sep 13 05:48:04 raspberrypi mtp-probe: bus: 1, device: 25 was not an MTP device
Sep 13 05:48:05 raspberrypi kernel: [ 6572.491851] scsi 0:0:0:0: Direct-Access USB Flash Disk 1100 PQ: 0 ANSI: 6
Sep 13 05:48:05 raspberrypi kernel: [ 6572.492586] sd 0:0:0:0: Attached scsi generic sg0 type 0
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493253] sd 0:0:0:0: [sda] 61736960 512-byte logical blocks: (31.6 GB/29.4 GiB)
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493639] sd 0:0:0:0: [sda] Write Protect is off
Sep 13 05:48:05 raspberrypi kernel: [ 6572.493663] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Sep 13 05:48:05 raspberrypi kernel: [ 6572.494095] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 13 05:48:05 raspberrypi kernel: [ 6572.498538] sda: sda1
Sep 13 05:48:05 raspberrypi kernel: [ 6572.500805] sd 0:0:0:0: [sda] Attached SCSI removable disk
Sep 13 05:48:06 raspberrypi kernel: [ 6572.599846] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Sep 13 05:48:06 raspberrypi kernel: [ 6572.599878] F2FS-fs (sda): Can't find valid F2FS filesystem in 1th superblock
Sep 13 05:48:06 raspberrypi kernel: [ 6572.600343] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Sep 13 05:48:06 raspberrypi kernel: [ 6572.600358] F2FS-fs (sda): Can't find valid F2FS filesystem in 2th superblock
Sep 13 05:48:06 raspberrypi systemd-udevd[3817]: sda: Process '/bin/mount /dev/sda /media/securitycam' failed with exit code 32.
Sep 13 05:48:06 raspberrypi usbmount[3825]: USAGE: /dev/sda:PTUUID="7f81bc38"PTTYPE="dos"
Sep 13 05:48:06 raspberrypi usbmount[3825]: /dev/sda does not contain a filesystem or disklabel
Sep 13 05:48:06 raspberrypi systemd-udevd[3817]: sda: Process '/usr/share/usbmount/usbmount add' failed with exit code 1.
Sep 13 05:48:06 raspberrypi usbmount[3845]: USAGE: filesystem
Sep 13 05:48:06 raspberrypi usbmount[3845]: executing command: mount -tvfat -osync,noexec,nodev,noatime,nodiratime,uid=jonas,gid=users,dmask=0002,fmask=0003 /dev/sda1 /media/usb0
Sep 13 05:48:06 raspberrypi kernel: [ 6573.003468] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Sep 13 05:48:06 raspberrypi usbmount[3845]: executing command: run-parts /etc/usbmount/mount.d
Here is what fdisk -l says about my USB-Device:
Disk /dev/sda: 29.44 GiB, 31609323520 bytes, 61736960 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7f81bc38
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 224 61736959 61736736 29.4G c W95 FAT32 (LBA)
My idea is that it has something to do with the Devicename. In syslog it says:
usbmount[3825]: /dev/sda does not contain a filesystem or disklabel
so maybe usbmount should look for /dev/sda1 which includes a filesystem
as you can see with the command:
sudo blkid -p /dev/sda1
/dev/sda1: LABEL="PHILIPS UFD" UUID="863A-2B54" VERSION="FAT32" BLOCK_SIZE="512" TYPE="vfat" USAGE="filesystem" PART_ENTRY_SCHEME="dos" PART_ENTRY_UUID="7f81bc38-01" PART_ENTRY_TYPE="0xc" PART_ENTRY_FLAGS="0x80" PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="224" PART_ENTRY_SIZE="61736736" PART_ENTRY_DISK="8:0"
Regrettably the bash script /usr/share/usbmount/usbmount has a variable called: $DEVNAME when it processes the condition "add" from the udev-rule and this variable includes /dev/sda as you can see in the syslog-file.
Is there a possibility to change the variable name or is my solution approach completely wrong?
I tried to realize a WebRTC communication, a RPi with a webcam to stream, and can be seen on web browser on another computer, both under the same WIFI
*RPi:
Collect streaming data.
WebRTC server
*Another computer: see the streaming image on web browser through WebRTC
*I choose UV4L to have WebRTC function.
After installing UV4L (I used uv4l-uvc) and
set the /etc/systemd/system/uv4l_raspicam.service
[Unit]
Description=UV4L Raspicam
[Service]
Type=simple
ExecStart=/usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.conf
Restart=on-abnormal
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target
then start the uv4l_raspicam service
sudo service uv4l_raspicam status
then check the status
● uv4l_raspicam.service - UV4L Raspicam
Loaded: loaded (/etc/systemd/system/uv4l_raspicam.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-06-20 17:05:24 CST; 55min ago
Main PID: 3922 (uv4l)
Tasks: 11 (limit: 1936)
CGroup: /system.slice/uv4l_raspicam.service
└─3922 /usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.conf
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] HTTP/HTTPS Streaming & WebRTC Signalling Server v1.1.130 built on Jan 16 2022
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [server] SSL is not enabled for the Streaming Server. Using unsecure HTTP.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Streaming Server loaded!
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [core] Cannot create /dev/video0 because file already exists
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Registering device node /dev/video1
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] Web Streaming Server listening on port 8090
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] WebRTC Renderer extension successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [server] WebRTC, Signalling Server and STUN Server extensions successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] STUN server listening to 0.0.0.0:3478
It seems that the service works fine.
I then tried to access http://rpihostname:8090/stream
it worked. The streaming from my webcam(on RPi) works.
However, when I tried http://rpihostname:8090/stream/webrtc
after pressing "call" button it stucked and nothing happened... then checked on the status of uv4l_raspicam, it still showed
● uv4l_raspicam.service - UV4L Raspicam
Loaded: loaded (/etc/systemd/system/uv4l_raspicam.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-06-20 17:05:24 CST; 55min ago
Main PID: 3922 (uv4l)
Tasks: 11 (limit: 1936)
CGroup: /system.slice/uv4l_raspicam.service
└─3922 /usr/bin/uv4l -f -k --sched-fifo --mem-lock --config-file=/etc/uv4l/uv4l-uvc.conf --driver=uvc --device-path=001:007 --driver-config-file=/etc/uv4l/uv4l-uvc.conf --server-option=--editable-config-file=/etc/uv4l/uv4l-uvc.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] HTTP/HTTPS Streaming & WebRTC Signalling Server v1.1.130 built on Jan 16 2022
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [server] SSL is not enabled for the Streaming Server. Using unsecure HTTP.
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Streaming Server loaded!
Jun 20 17:05:24 raspberrypi uv4l[3922]: <warning> [core] Cannot create /dev/video0 because file already exists
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [core] Registering device node /dev/video1
Jun 20 17:05:24 raspberrypi uv4l[3922]: <notice> [server] Web Streaming Server listening on port 8090
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] WebRTC Renderer extension successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [server] WebRTC, Signalling Server and STUN Server extensions successfully loaded
Jun 20 17:06:06 raspberrypi uv4l[3922]: <notice> [webrtc] STUN server listening to 0.0.0.0:3478
Any comments on this? Thanks in advance!
I need to configure the [TRM240 modem][1] to work with a Raspbian system. I followed the procedure reported in the answer [here][2], but the connection isn't working.
I attach some screenshots documenting the procedure and the commands that I issued.
First, look for connected modems:
pi#raspberrypi:~ $ mmcli -L
Found 1 modems:
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL Mobile Broadband Module
Check the unique modem found:
pi#raspberrypi:~ $ mmcli -m 0
/org/freedesktop/ModemManager1/Modem/0 (device id 'e308f44de689f834e8cbc5b2122a4ffca8ddd3f5')
-------------------------
Hardware | manufacturer: 'QUALCOMM INCORPORATED'
| model: 'QUECTEL Mobile Broadband Module'
| revision: 'EC21ECGAR06A04M1G'
| supported: 'gsm-umts
| lte
| gsm-umts, lte'
| current: 'gsm-umts, lte'
| equipment id: '864394040056931'
-------------------------
System | device: '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2'
| drivers: 'option1, qmi_wwan'
| plugin: 'Generic'
| primary port: 'cdc-wdm0'
| ports: 'ttyUSB0 (qcdm), ttyUSB2 (at), cdc-wdm0 (qmi), wwan0 (net), ttyUSB3 (at)'
-------------------------
Numbers | own : 'unknown'
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
| current: 'allowed: any; preferred: none'
-------------------------
Bands | supported: 'unknown'
| current: 'unknown'
-------------------------
IP | supported: 'ipv4, ipv6, ipv4v6'
-------------------------
SIM | path: 'none'
-------------------------
Bearers | paths: 'none'
Here, the Status section leaves me a little bit puzzled, but I try to go on.
I tried the following command using different options for ifname: cdc-wdm0, ttyUSB2 and ttyUSB3. They all end up to the same result.
pi#raspberrypi:~ $ sudo nmcli c add type gsm ifname cdc-wdm0 con-name modem apn mobile.vodafone.it
Connection 'modem' (9c34027f-5df5-4fd6-9792-223e225dfd41) successfully added.
Check the connections and try to take up modem:
pi#raspberrypi:~ $ nmcli con
NAME UUID TYPE DEVICE
br-12ff13c2c4e0 26450e11-6671-47c2-91af-6bf96405921b bridge br-12ff13c2c4e0
br-acc4bdcbe6e7 440cfcc0-5318-4a9e-9259-3fb8700cf240 bridge br-acc4bdcbe6e7
docker0 8af67071-3cb2-4235-882f-1cc1f50fa7ca bridge docker0
modem 9c34027f-5df5-4fd6-9792-223e225dfd41 gsm --
Try to take up:
pi#raspberrypi:~ $ nmcli con up modem
Error: Connection activation failed: No suitable device found for this connection.
Status of service NetworkManager:
pi#raspberrypi:~ $ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Docs: man:NetworkManager(8)
Main PID: 710 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 13.8M
CPU: 3.862s
CGroup: /system.slice/NetworkManager.service
└─710 /usr/sbin/NetworkManager --no-daemon
Aug 21 07:48:53 raspberrypi NetworkManager[710]: <info> [1597996133.0883] device (veth6ffb100): link connected
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported
Aug 21 08:14:11 raspberrypi NetworkManager[710]: <info> [1597997651.4343] audit: op="device-managed" arg="managed:1" pid=11841 uid=0 result="success"
Aug 21 08:16:48 raspberrypi NetworkManager[710]: <info> [1597997808.9388] audit: op="device-autoconnect" arg="autoconnect:1" pid=12910 uid=1000 result="fail" reason="Not authorized to perform this operat
Aug 21 08:17:41 raspberrypi NetworkManager[710]: <info> [1597997861.0575] audit: op="connection-add-activate" pid=13286 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 08:25:25 raspberrypi NetworkManager[710]: <info> [1597998325.2594] audit: op="connection-add-activate" pid=16224 uid=1000 result="fail" reason="gsm: GSM mobile broadband connection requires a 'gsm
Aug 21 10:06:31 raspberrypi NetworkManager[710]: <info> [1598004391.9223] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3349] keyfile: add connection /etc/NetworkManager/system-connections/modem-9c34027f-5df5-4fd6-9792-223e225dfd41 (9c34027f-5df5-4fd6-979
Aug 21 10:19:24 raspberrypi NetworkManager[710]: <info> [1598005164.3386] audit: op="connection-add" uuid="9c34027f-5df5-4fd6-9792-223e225dfd41" name="modem" pid=27261 uid=0 result="success"
Aug 21 10:20:29 raspberrypi NetworkManager[710]: <info> [1598005229.6409] audit: op="connection-activate" uuid="06583333-e03e-431f-9376-94c38b6b607d" name="modem" result="fail" reason="No suitable device
lines 1-21/21 (END)
Here I see the error <error> [1597997651.4341] audit: failed to open auditd socket: Protocol not supported...
Status of service ModemManager (there are warnings, but not errors):
pi#raspberrypi:~ $ systemctl status ModemManager
● ModemManager.service - Modem Manager
Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-21 07:46:57 UTC; 2h 35min ago
Main PID: 712 (ModemManager)
Tasks: 5 (limit: 4915)
Memory: 8.7M
CPU: 4.123s
CGroup: /system.slice/ModemManager.service
├─712 /usr/sbin/ModemManager
└─884 /usr/lib/libqmi/qmi-proxy
Aug 21 07:47:19 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'nas' (version 1.25) client with ID '2'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'wms' (version 1.10) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Allocating new client ID...
Aug 21 07:47:20 raspberrypi ModemManager[712]: [/dev/cdc-wdm0] Registered 'uim' (version 1.46) client with ID '1'
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> (ttyUSB2): port attributes not fully set
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Supported Bands: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:20 raspberrypi ModemManager[712]: <warn> couldn't load Power State: 'QMI operation failed: Cannot send message: QMI service 'dms' version '1.1' required, got version '1.0''
Aug 21 07:47:55 raspberrypi ModemManager[712]: <warn> Modem couldn't be initialized: Couldn't check unlock status: Couldn't get SIM lock status after 6 retries
Aug 21 07:47:55 raspberrypi ModemManager[712]: <info> Modem: state changed (unknown -> failed)
System info:
pi#raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
pi#raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch
It may be that the SIM is not working properly or the modem is not recognizing it.
This is what the output
-------------------------
Status | lock: 'unknown'
| unlock retries: 'unknown'
| state: 'failed'
| failed reason: 'sim-missing'
| power state: 'unknown'
| access tech: 'unknown'
| signal quality: '0' (cached)
-------------------------
points out.
Check this answer.
(I didn't find it before posting my question.)
I'm using an Arduino Nano, previously an UNO, to collect data from sensors and then send the data back over a USB connection through a powered hub to a Raspberry Pi model B running Jessie 4.1.19+ Mar, 15 2016 and Python 2.7. The python code uses pyserial readline to get the data.
In general it works fine but occasionally (typically a couple of times a day) it fails with the above message. It seemed the only way to fix it was to unplug the USB connection, reconnect it and restart the program. I altered the code to catch the exception but it wouldn't reopen the connection, giving the error:
serial.serialutil.SerialException: could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'
This problem occurs with both the UNO (on /dev/ttyAMA0) and the NANO (on /dev/ttyUSB0).
Just recently I discovered that following this fault the Nano had moved to /dev/ttyUSB1. The python code will then run successfully against /dev/ttyUSB1 but when the problem occurs again it switches back to /dev/ttyUSB0.
As a result, I have changed the code to intercept the exception and open the alternative device and carry on. So far this is working fine but its clearly not right.
Can anyone suggest where the problem might lie and how I could go about diagnosing it? I'm not super-technical! Also, I've seen a couple of other posts on this subject but reverting back to a previous kernel level is not really practical in this instance.
Updated to include log output below. There are two devices: NANO (1a86:7523) and an OWL power monitor (0fde:ca05).
$ dmesg -T
[Sat Feb 11 14:53:02 2017] usb 1-1.3-port2: disabled by hub (EMI?), re-enabling...
[Sat Feb 11 14:53:02 2017] usb 1-1.3.2: USB disconnect, device number 71
[Sat Feb 11 14:53:03 2017] dwc_otg_hcd_handle_hc_fsm: 173 callbacks suppressed
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1649 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1650 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1651 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1652 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1653 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1654 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1655 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1656 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1657 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] Transfer to device 72 endpoint 0x1 frame 1658 failed - FIQ reported NYET. Data may have been lost.
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: new full-speed USB device number 73 using dwc_otg
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: New USB device found, idVendor=0fde, idProduct=ca05
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: Product: OWL Wireless Electricity Monitor USB version is connected
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: Manufacturer: Silicon Labs
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: SerialNumber: 001A3C26
[Sat Feb 11 14:53:03 2017] cp210x 1-1.3.2:1.0: cp210x converter detected
[Sat Feb 11 14:53:03 2017] usb 1-1.3.2: cp210x converter now attached to ttyUSB0
[Sat Feb 11 14:53:03 2017] usb 1-1.3-port3: disabled by hub (EMI?), re-enabling...
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: USB disconnect, device number 72
[Sat Feb 11 14:53:03 2017] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[Sat Feb 11 14:53:03 2017] ch341 1-1.3.3:1.0: device disconnected
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: new full-speed USB device number 74 using dwc_otg
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: New USB device found, idVendor=1a86, idProduct=7523
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: Product: USB2.0-Serial
[Sat Feb 11 14:53:03 2017] ch341 1-1.3.3:1.0: ch341-uart converter detected
[Sat Feb 11 14:53:03 2017] usb 1-1.3.3: ch341-uart converter now attached to ttyUSB2
[Sat Feb 11 14:53:05 2017] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[Sat Feb 11 14:53:05 2017] cp210x 1-1.3.2:1.0: device disconnected
I know this is an old thread but I hit this issue recently with my Raspberry Pi 3 Model B Rev 1.2 running a stock Debian kernel 5.4.0-3-arm64 while connecting a 3018 CNC Pro controller board. When I lsusb, the board appears as
Bus 001 Device 011: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Whenever I would open the serial port, the usb device would reset. I searched far and wide, applied a bunch of config parameters from different forums but the issue turned out to be power-related for me.
While the 3018 CNC Pro board has an independent power supply, the usb-serial chip on the board is bus-powered (noticed this in lsusb -v). My Raspberry Pi has plenty of available power but I was running the 1m usb cable through a metal clip and along a metal channel which must have had enough inductance to resist the required surge of power through the usb cable. Removing the clip solved the problem.
Hopefully this note helps someone!
I'm trying to build an access point / hotspot with a Raspberry Pi, a wifi dongle and NetworkManager. I know that I can achieve this by just working with hostapd, dnsmasq and ifupdown - I even had it working with this. But I would like to use NetworkManager, as there is a nice Lib I can use to toggle the connections with Python. When reading about Network Manager it says that there are 3 kind of "modes" I can use. "Infrastructure", "ap" and "adhoc" - Infrastracture and "adhoc" are working, but not the ap one, which I need. This is what the Logs are giving me.
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: updating /etc/NetworkManager/system-connections/Hotspot_safe_save_075806
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: error: File did not exist or was not a regular file
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: updating /etc/NetworkManager/system-connections/Hotspot_safe_save_075806
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: error: File did not exist or was not a regular file
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: removed /etc/NetworkManager/system-connections/Hotspot.
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: updating /etc/NetworkManager/system-connections/Hotspot
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: error: invalid or missing connection property 'mode'
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: updating /etc/NetworkManager/system-connections/Hotspot
Jun 22 00:08:09 raspberrypi NetworkManager[2760]: keyfile: error: invalid or missing connection property 'mode'
What am I doing wrong? I Read that it could be that i need to recompile wpasupplicant - but with this i got some trouble. Any help appreciated.
Problem was that I was trying to do this with an Raspbian (Debian) Wheezy Image, which has an older NetworkManager. With the Jessie Image everything is working like a breeze now.
I could have compiled the newer NetworkManager by myself, but my skill level therefore is not that high ;)