My new Arch installation always stucks after rebooting with the Message [x.yz] Bluetooth: hci0: Reading supported features failed (-16). It is just doing nothing until I start a session on tty2 by pressing CTRL+ALT+F2 and going back to CTRL+ALT+F1 without logging in in tty2 (btw. I have installed gnome with gdm). Bluetooth is working well once I'm logged in...
Here are all journalctl - b-Outputs containing 'Bluetooth':
Mar 06 14:56:23 archBook kernel: Bluetooth: Core ver 2.22
Mar 06 14:56:23 archBook kernel: Bluetooth: HCI device and connection manager initialized
Mar 06 14:56:23 archBook kernel: Bluetooth: HCI socket layer initialized
Mar 06 14:56:23 archBook kernel: Bluetooth: L2CAP socket layer initialized
Mar 06 14:56:23 archBook kernel: Bluetooth: SCO socket layer initialized
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Device revision is 16
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Secure boot is enabled
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: OTP lock is enabled
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: API lock is enabled
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Debug lock is disabled
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Mar 06 14:56:23 archBook kernel: Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
Mar 06 14:56:23 archBook systemd[1]: Starting Bluetooth service...
Mar 06 14:56:23 archBook bluetoothd[392]: Bluetooth daemon 5.56
Mar 06 14:56:23 archBook systemd[1]: Started Bluetooth service.
Mar 06 14:56:23 archBook systemd[1]: Reached target Bluetooth.
Mar 06 14:56:23 archBook kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 06 14:56:23 archBook kernel: Bluetooth: BNEP filters: protocol multicast
Mar 06 14:56:23 archBook kernel: Bluetooth: BNEP socket layer initialized
Mar 06 14:56:23 archBook bluetoothd[392]: Bluetooth management interface 1.19 initialized
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Waiting for firmware download to complete
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Firmware loaded in 1675919 usecs
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Waiting for device to boot
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Device booted in 11722 usecs
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Reading supported features failed (-16)
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Telemetry exception format not supported
Mar 06 14:56:25 archBook kernel: Bluetooth: hci0: Firmware revision 0.1 build 50 week 12 2019
Mar 06 15:01:32 archBook kernel: Bluetooth: RFCOMM TTY layer initialized
Mar 06 15:01:32 archBook kernel: Bluetooth: RFCOMM socket layer initialized
Mar 06 15:01:32 archBook kernel: Bluetooth: RFCOMM ver 1.11
Mar 06 15:01:36 archBook systemd[749]: Starting Bluetooth OBEX service...
Mar 06 15:01:36 archBook systemd[749]: Started Bluetooth OBEX service.
Hope somebody can help me to fix this since it sucks to always enter tty2 before I can log in via GUI...
Thanks for any advice and tell me if you need more information
Related
I have a Quectel EG25-G setup but whenever I connect (right after a reboot) it connects for 20 seconds and then disconnects.
It happens at the
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4569] device (ttyUSB2): state change: activated -> failed (reason 'modem-no-carrier', sys-iface-state: 'managed')
Jun 24 04:59:32 linux NetworkManager[5093]: <warn> [1656046772.4677] device (ttyUSB2): Activation: failed for connection 'telstra'
point but I can't read why this is happening.
Can someone point me in the right direction please ?
configuration:
nvidia#localhost:~$ sudo cat /etc/NetworkManager/system-connections/telstra
[sudo] password for nvidia:
[connection]
id=telstra
uuid=9ae31580-093b-45ec-8b8c-3c22e7eca76f
type=gsm
permissions=
[gsm]
apn=telstra.internet
number=*99#
password-flags=1
[ipv4]
dns-search=
method=auto
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=auto
output of NetworkManager and ping google.com :
nvidia#localhost:~$ journalctl -u NetworkManager -f &
[1] 7916
nvidia#localhost:~$ ping google.com &-- Logs begin at Fri 2022-06-24 04:58:32 UTC. --
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0549] device (l4tbr0): Activation: starting connection 'l4tbr0' (73df77e3-1d83-4794-afcb-e6079b37272b)
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0575] device (l4tbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0602] device (l4tbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0609] device (l4tbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0612] device (l4tbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0628] device (l4tbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0636] device (l4tbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Jun 24 04:58:39 localhost.localdomain NetworkManager[5093]: <info> [1656046719.0681] device (l4tbr0): Activation: successful, device activated.
Jun 24 04:58:41 localhost.localdomain NetworkManager[5093]: <info> [1656046721.6864] manager: startup complete
Jun 24 04:58:43 localhost.localdomain NetworkManager[5093]: <info> [1656046723.1537] bluez: use BlueZ version 5
[2] 7917
nvidia#localhost:~$ ping: google.com: Name or service not known
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.7954] modem["ttyUSB2"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.7970] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/10)
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.7976] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.7983] device (ttyUSB2): modem state 'enabling'
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.7997] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.8004] policy: auto-activating connection 'telstra'
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.8025] device (ttyUSB2): Activation: starting connection 'telstra' (9ae31580-093b-45ec-8b8c-3c22e7eca76f)
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.8030] device (ttyUSB2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:01 localhost.localdomain NetworkManager[5093]: <info> [1656046741.8032] manager: NetworkManager state is now CONNECTING
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.5602] modem["ttyUSB2"]: modem state changed, 'enabling' --> 'enabled' (reason: user-requested)
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.6982] modem["ttyUSB2"]: modem state changed, 'enabled' --> 'registered' (reason: unknown)
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.7381] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8055] modem["ttyUSB2"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested)
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <warn> [1656046742.8173] device (ttyUSB2): ip-ifname: set ifname 'ttyUSB2', unknown ifindex
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8177] device (ttyUSB2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8183] device (ttyUSB2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <warn> [1656046742.8190] device (ttyUSB2): interface ttyUSB2 not up for IP configuration
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8191] modem["ttyUSB2"]: using modem-specified IP timeout: 20 seconds
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8253] loaded PPP plugin /usr/lib/aarch64-linux-gnu/NetworkManager/libnm-ppp-plugin.so
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8264] ppp-manager: starting PPP connection
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8317] ppp-manager: pppd started with pid 7929
Jun 24 04:59:02 localhost.localdomain pppd[7929]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: Plugin /usr/lib/pppd/2.4.7/nm-pppd-plugin.so loaded.
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (plugin_init): initializing
Jun 24 04:59:02 localhost.localdomain pppd[7929]: pppd 2.4.7 started by root, uid 0
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
Jun 24 04:59:02 localhost.localdomain pppd[7929]: Using interface ppp0
Jun 24 04:59:02 localhost.localdomain pppd[7929]: Connect: ppp0 <--> /dev/ttyUSB2
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: Using interface ppp0
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: Connect: ppp0 <--> /dev/ttyUSB2
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8628] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/11)
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate'
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (get_credentials): passwd-hook, requesting credentials...
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (get_credentials): got credentials from NetworkManager
Jun 24 04:59:02 localhost.localdomain pppd[7929]: CHAP authentication succeeded
Jun 24 04:59:02 localhost.localdomain pppd[7929]: CHAP authentication succeeded
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: CHAP authentication succeeded
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8875] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.8875] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jun 24 04:59:02 localhost.localdomain pppd[7929]: Could not determine remote IP address: defaulting to 10.64.64.64
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: Could not determine remote IP address: defaulting to 10.64.64.64
Jun 24 04:59:02 localhost.localdomain pppd[7929]: local IP address 10.247.106.201
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: local IP address 10.247.106.201
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: remote IP address 10.64.64.64
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: primary DNS address 101.168.244.101
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: secondary DNS address 101.168.244.103
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_phasechange): status 9 / phase 'running'
Jun 24 04:59:02 localhost.localdomain pppd[7929]: remote IP address 10.64.64.64
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_ip_up): ip-up event
Jun 24 04:59:02 localhost.localdomain pppd[7929]: primary DNS address 101.168.244.101
Jun 24 04:59:02 localhost.localdomain pppd[7929]: nm-ppp-plugin: (nm_ip_up): sending IPv4 config to NetworkManager...
Jun 24 04:59:02 localhost.localdomain pppd[7929]: secondary DNS address 101.168.244.103
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9212] ppp-manager: (IPv4 Config Get) reply received.
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9268] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9297] device (ttyUSB2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9341] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9350] device (ttyUSB2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9356] device (ttyUSB2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9359] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9387] manager: NetworkManager state is now CONNECTED_SITE
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9391] policy: set 'telstra' (ppp0) as default for IPv4 routing and DNS
Jun 24 04:59:02 localhost.localdomain NetworkManager[5093]: <info> [1656046742.9437] device (ttyUSB2): Activation: successful, device activated.
Jun 24 04:59:03 localhost.localdomain NetworkManager[5093]: <info> [1656046743.1280] policy: set-hostname: set hostname to 'linux' (from address lookup)
Jun 24 04:59:03 linux NetworkManager[5093]: <info> [1656046743.9009] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 24 04:59:05 linux pppd[7929]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 2613)
Jun 24 04:59:05 linux NetworkManager[5093]: sif6addr: ioctl(SIOCSIFADDR): Permission denied (line 2613)
Jun 24 04:59:05 linux NetworkManager[5093]: cif6addr: ioctl(SIOCDIFADDR): No such address
Jun 24 04:59:05 linux pppd[7929]: cif6addr: ioctl(SIOCDIFADDR): No such address
[2]+ Exit 2 ping google.com
nvidia#localhost:~$
nvidia#localhost:~$ ping google.com
PING google.com (172.217.24.46) 56(84) bytes of data.
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=1 ttl=115 time=34.7 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=2 ttl=115 time=74.3 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=3 ttl=115 time=71.4 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=4 ttl=115 time=55.9 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=5 ttl=115 time=54.4 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=6 ttl=115 time=52.7 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=7 ttl=115 time=51.7 ms
64 bytes from hkg07s23-in-f14.1e100.net (172.217.24.46): icmp_seq=8 ttl=115 time=52.0 ms
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4567] modem["ttyUSB2"]: modem state changed, 'connected' --> 'registered' (reason: user-requested)
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4569] device (ttyUSB2): state change: activated -> failed (reason 'modem-no-carrier', sys-iface-state: 'managed')
Jun 24 04:59:32 linux NetworkManager[5093]: <warn> [1656046772.4677] device (ttyUSB2): Activation: failed for connection 'telstra'
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4690] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4711] device (ttyUSB2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4955] policy: set-hostname: set hostname to 'localhost.localdomain' (no default device)
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4965] device (ppp0): state change: disconnected -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external')
Jun 24 04:59:32 linux NetworkManager[5093]: <info> [1656046772.4985] policy: auto-activating connection 'telstra'
Jun 24 04:59:32 localhost.localdomain NetworkManager[5093]: <info> [1656046772.5016] device (ttyUSB2): Activation: starting connection 'telstra' (9ae31580-093b-45ec-8b8c-3c22e7eca76f)
Jun 24 04:59:32 localhost.localdomain NetworkManager[5093]: <info> [1656046772.5035] device (ttyUSB2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:32 localhost.localdomain NetworkManager[5093]: <info> [1656046772.5038] manager: NetworkManager state is now CONNECTING
Jun 24 04:59:32 localhost.localdomain NetworkManager[5093]: <info> [1656046772.5361] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 24 04:59:39 localhost.localdomain NetworkManager[5093]: <info> [1656046779.6407] modem["ttyUSB2"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jun 24 04:59:39 localhost.localdomain NetworkManager[5093]: <info> [1656046779.6622] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 24 04:59:46 localhost.localdomain NetworkManager[5093]: <info> [1656046786.7669] modem["ttyUSB2"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jun 24 04:59:46 localhost.localdomain NetworkManager[5093]: <info> [1656046786.7880] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.8956] modem["ttyUSB2"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <warn> [1656046793.8960] modem-broadband[ttyUSB2]: failed to connect modem: Sending command failed: 'Resource temporarily unavailable'
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.8962] device (ttyUSB2): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.8971] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <warn> [1656046793.8988] device (ttyUSB2): Activation: failed for connection 'telstra'
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9007] device (ttyUSB2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9028] policy: auto-activating connection 'telstra'
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9052] device (ttyUSB2): Activation: starting connection 'telstra' (9ae31580-093b-45ec-8b8c-3c22e7eca76f)
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9064] device (ttyUSB2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9072] manager: NetworkManager state is now CONNECTING
Jun 24 04:59:53 localhost.localdomain NetworkManager[5093]: <info> [1656046793.9246] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jun 24 05:00:01 localhost.localdomain NetworkManager[5093]: <info> [1656046801.0289] modem["ttyUSB2"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jun 24 05:00:01 localhost.localdomain NetworkManager[5093]: <info> [1656046801.0454] modem["ttyUSB2"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested)
... etc...
seeing i can't delete this and i've found the answer:
Someone here suggested to update to the latest ModemManager like:
Code:
sudo apt-get install software-properties-common # contains add-apt-repository
sudo add-apt-repository ppa:aleksander-m/modemmanager-bionic
sudo apt-get update
sudo apt-get install modemmanager libqmi-utils libmbim-utils policykit-1
sudo reboot
and it all started working. Must have been a a ModemHandler bug in the older verision of ModemManager that the base image of NVidia comes with.
I'm working on non-Linux OS and now trying to enable bluetooth on Raspberry Pi 4.
I have some necessary drivers such as: gpio, uart (pl011 and mini-uart), mailbox and expgpio through that mailbox.
To enable bluetooth I make some steps:
I configure GPIOs as described in Linux's dts to make UART0 connected
to BT/WiFi chip;
I set BT_ON expgpio to 1 through mailbox (it is made by default, just ensure);
I wrote some command to UART0 and nothing happened =( UART driver return success and reading command answer is always timeouted.
I think I could forget some step for initialization procedure, but as I can see in Linux log there is only firmware downloading and many commands, such as read device name, can be executed prior to it.
May be I forget to enable some clock source or a regulator, but I don't have any idea where start my research.
There is a part of Raspbian kernel log with additional debug info:
Jan 28 05:17:13 raspberrypi kernel: [ 15.321055] Bluetooth: Core ver 2.22
Jan 28 05:17:13 raspberrypi kernel: [ 15.321093] device class 'bluetooth': registering
Jan 28 05:17:13 raspberrypi kernel: [ 15.321149] NET: Registered PF_BLUETOOTH protocol family
Jan 28 05:17:13 raspberrypi kernel: [ 15.321158] Bluetooth: HCI device and connection manager initialized
Jan 28 05:17:13 raspberrypi kernel: [ 15.321176] Bluetooth: HCI socket layer initialized
Jan 28 05:17:13 raspberrypi kernel: [ 15.321189] Bluetooth: L2CAP socket layer initialized
Jan 28 05:17:13 raspberrypi kernel: [ 15.321208] Bluetooth: SCO socket layer initialized
Jan 28 05:17:13 raspberrypi kernel: [ 15.335356] Bluetooth: HCI UART driver ver 2.3
Jan 28 05:17:13 raspberrypi kernel: [ 15.335377] Bluetooth: HCI UART protocol H4 registered at id 0
Jan 28 05:17:13 raspberrypi kernel: [ 15.335387] bus: 'serial': add driver hci_uart_h5
Jan 28 05:17:13 raspberrypi kernel: [ 15.335456] Bluetooth: HCI UART protocol Three-wire (H5) registered at id 2
Jan 28 05:17:13 raspberrypi kernel: [ 15.335480] bus: 'platform': add driver hci_bcm
Jan 28 05:17:13 raspberrypi kernel: [ 15.335641] bus: 'serial': add driver hci_uart_bcm
Jan 28 05:17:13 raspberrypi kernel: [ 15.335679] Bluetooth: HCI UART protocol Broadcom registered at id 7
Jan 28 05:17:13 raspberrypi kernel: [ 15.337922] Bluetooth: TTY name ttyAMA0
Jan 28 05:17:13 raspberrypi kernel: [ 15.338543] Bluetooth: hci_uart_register_dev
Jan 28 05:17:13 raspberrypi kernel: [ 15.338599] device: 'hci0': device_add
Jan 28 05:17:13 raspberrypi kernel: [ 15.345358] device: 'rfkill1': device_add
Jan 28 05:17:13 raspberrypi kernel: [ 15.345497] Bluetooth: HCI UART protocol set. Proto H4; id 0
Jan 28 05:17:13 raspberrypi kernel: [ 15.345530] Bluetooth: hci_uart_open hci0 5d898f04
Jan 28 05:17:13 raspberrypi kernel: [ 15.345543] Bluetooth: hci_uart_setup: START
Jan 28 05:17:13 raspberrypi kernel: [ 15.345550] Bluetooth: hci_uart_setup: init speed = 0
Jan 28 05:17:13 raspberrypi kernel: [ 15.345557] Bluetooth: hci_uart_setup: oper speed = 0
Jan 28 05:17:13 raspberrypi kernel: [ 15.352975] Bluetooth: hci0: type 1 len 3
Jan 28 05:17:13 raspberrypi kernel: [ 15.353010] Bluetooth skb: 00000000: 01 03 10 00
Jan 28 05:17:13 raspberrypi kernel: [ 15.353026] Bluetooth: hci_uart_write_work written 4
Jan 28 05:17:13 raspberrypi kernel: [ 15.353760] Bluetooth: hci0: type 1 len 3
Jan 28 05:17:13 raspberrypi kernel: [ 15.353826] Bluetooth skb: 00000000: 01 01 10 00
....
a lot of lines
....
Jan 28 05:17:13 raspberrypi btuart[479]: bcm43xx_init
Jan 28 05:17:13 raspberrypi btuart[479]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Jan 28 05:17:13 raspberrypi btuart[479]: Set Controller UART speed to 3000000 bit/s
Jan 28 05:17:13 raspberrypi btuart[479]: Device setup complete
Jan 28 05:17:13 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 28 05:17:13 raspberrypi systemd[1]: Started Configure Bluetooth Modems connected by UART.
Jan 28 05:17:13 raspberrypi systemd[1]: Reached target Multi-User System.
Jan 28 05:17:13 raspberrypi systemd[1]: Reached target Graphical Interface.
Jan 28 05:17:13 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jan 28 05:17:13 raspberrypi systemd[625]: Reached target Bluetooth.
Jan 28 05:17:13 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 28 05:17:13 raspberrypi systemd[1]: Created slice system-bthelper.slice.
Jan 28 05:17:13 raspberrypi systemd[1]: Starting Raspberry Pi bluetooth helper...
Jan 28 05:17:13 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jan 28 05:17:13 raspberrypi systemd[1]: Finished Update UTMP about System Runlevel Changes.
Jan 28 05:17:13 raspberrypi bthelper[774]: Raspberry Pi BDADDR already set
Jan 28 05:17:13 raspberrypi systemd[1]: Finished Raspberry Pi bluetooth helper.
Jan 28 05:17:13 raspberrypi kernel: [ 15.490868] Bluetooth: hci0: type 1 len 8
Jan 28 05:17:13 raspberrypi kernel: [ 15.490909] Bluetooth skb: 00000000: 01 1c fc 05 01 02 00 01 01
Jan 28 05:17:13 raspberrypi kernel: [ 15.490930] Bluetooth: hci_uart_write_work written 9
Thank you in advance
For H4 protocol UART with Hardware Flow Control must be used. Adding HFC support to PL011 UART driver resolves the problem.
My laptop is suspending on lid close successfully, but if I don't have it plugged in overnight, the battery is drained by the morning.
I'm including logs from a short suspend I ran just now. I can suspend it overnight and look at the logs afterward, but is there anything immediately suspicious here? I validated that all suspend-related targets are loaded via sudo systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target
Apr 11 22:09:29 pop-os systemd[1]: Reached target Sleep.
Apr 11 22:09:29 pop-os systemd[1]: Starting Suspend...
Apr 11 22:09:29 pop-os kernel: [ 44.986190] PM: suspend entry (s2idle)
Apr 11 22:09:29 pop-os systemd-sleep[3730]: Suspending system...
Apr 11 22:09:29 pop-os kernel: [ 44.991600] Filesystems sync: 0.005 seconds
Apr 11 22:09:57 pop-os kernel: [ 44.994638] Freezing user space processes ... (elapsed 0.002 seconds) done.
Apr 11 22:09:57 pop-os kernel: [ 44.996920] OOM killer disabled.
Apr 11 22:09:57 pop-os kernel: [ 44.996921] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr 11 22:09:57 pop-os kernel: [ 44.998055] printk: Suspending console(s) (use no_console_suspend to debug)
Apr 11 22:09:57 pop-os kernel: [ 45.315954] psmouse serio1: Failed to disable mouse on isa0060/serio1
Apr 11 22:09:57 pop-os kernel: [ 46.377203] ACPI: EC: interrupt blocked
Apr 11 22:09:57 pop-os kernel: [ 72.605807] ACPI: EC: interrupt unblocked
Apr 11 22:09:57 pop-os kernel: [ 73.107660] pcieport 10000:e0:06.0: can't derive routing for PCI INT A
Apr 11 22:09:57 pop-os kernel: [ 73.107666] nvme 10000:e1:00.0: PCI INT A: no GSI
Apr 11 22:09:57 pop-os kernel: [ 73.114494] nvme nvme0: 8/0/0 default/read/poll queues
Apr 11 22:09:57 pop-os kernel: [ 73.363725] OOM killer enabled.
Apr 11 22:09:57 pop-os kernel: [ 73.363728] Restarting tasks ...
Apr 11 22:09:57 pop-os kernel: [ 73.364154] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Apr 11 22:09:57 pop-os kernel: [ 73.367166] done.
Apr 11 22:09:57 pop-os touchegg[1000]: libinput error: event0 - Lid Switch: client bug: event processing lagging behind by 1279ms, your system is too slow
Apr 11 22:09:57 pop-os /usr/libexec/gdm-x-session[1823]: (II) modeset(0): EDID vendor "SHP", prod id 5370
Apr 11 22:09:57 pop-os /usr/libexec/gdm-x-session[1823]: (II) modeset(0): Printing DDC gathered Modelines:
Apr 11 22:09:57 pop-os /usr/libexec/gdm-x-session[1823]: (II) modeset(0): Modeline "3840x2400"x0.0 592.50 3840 3888 3920 4000 2400 2403 2409 2469 -hsync -vsync (148.1 kHz eP)
Apr 11 22:09:57 pop-os /usr/libexec/gdm-x-session[1823]: (II) modeset(0): Modeline "3840x2400"x0.0 474.00 3840 3888 3920 4000 2400 2403 2409 2469 -hsync -vsync (118.5 kHz e)
Apr 11 22:09:57 pop-os systemd-sleep[3730]: System resumed.
Apr 11 22:09:57 pop-os bluetoothd[961]: Controller resume with wake event 0x0
Apr 11 22:09:57 pop-os kernel: [ 73.413202] PM: suspend exit
Apr 11 22:09:57 pop-os systemd[1]: systemd-suspend.service: Succeeded.
Apr 11 22:09:57 pop-os systemd[1]: Finished Suspend.
Apr 11 22:09:57 pop-os systemd[1]: Stopped target Sleep.
Apr 11 22:09:57 pop-os systemd[1]: Reached target Suspend.
Apr 11 22:09:57 pop-os systemd[1]: Stopped target Suspend.
Apr 11 22:09:57 pop-os NetworkManager[968]: <info> [1649729397.3461] manager: sleep: wake requested (sleeping: yes enabled: yes)
Apr 11 22:09:57 pop-os NetworkManager[968]: <info> [1649729397.3461] device (wlp113s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 11 22:09:57 pop-os ModemManager[1079]: <info> [sleep-monitor] system is resuming
Apr 11 22:09:57 pop-os NetworkManager[968]: <info> [1649729397.4258] manager: NetworkManager state is now DISCONNECTED
The hardware on this system only supports s2idle sleep, and not deep sleep for less energy consumption (details on different sleep states here https://www.kernel.org/doc/Documentation/power/states.txt).
pop-os:$~ sudo cat /sys/power/mem_sleep
[s2idle]
I found this thread: https://www.dell.com/community/XPS/XPS-13-9310-Ubuntu-deep-sleep-missing/td-p/7734008 It suggests changing the disk management from RAID (Dell's default) to AHCI via the Dell BIOS.
So far this has worked for a solution! I've lost only 10% battery overnight, and can go 3 days idling in suspend without a charge.
(Before this, I did try enabling hibernate through these instructions from System76 https://support.system76.com/articles/enable-hibernation/. This does not work great, because the Killer wifi driver does not load on wake from hibernate.)
Suspend ( considering hybrid suspend ), the machine's state is stored in swap space and suspend via RAM (aka sleep) is invoked. This caused for minimal utilisation of power.
Reason to do so : wake up from hibernate is slower than wakeup from sleep. So to ensure system state is not lost, machine's state is stored in swap space and sleep is invoked that uses minimal power and does not shut off the machine. Machine's state is stored in RAM. If battery does not die, wake up happens from RAM which is faster.
Read More : https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate
In case you want your battery to not die or drain, switch your lid close action from sleep/suspend to hibernate. Hibernate has zero power consumption. Follow the steps mentioned below.
$ grep HandleLidSwitch /etc/systemd/logind.conf
HandleLidSwitch=suspend
If the line is commented, please uncomment by removing "#" and change option to hibernate.
HandleLidSwitch=hibernate
If you are new to Linux, please use gedit command to edit the file.
sudo gedit /etc/systemd/logind.conf
when i run yum command：
> yum
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
/usr/lib64/python2.6/lib-dynload/arraymodule.so: cannot read file data: Input/output error
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-11)]
Current version of Python is 2.6.6，not other。
system logs:
Oct 16 09:56:50 localhost kernel: mptbase: ioc0: LogInfo(0x31080000): Originator={PL}, Code={SATA NCQ Fail All Commands After Error}, SubCode(0x0000) cb_idx mptscsih_io_done
Oct 16 09:56:50 localhost kernel: LSI Debug log info 31080000 for channel 0 id 0
Oct 16 09:56:50 localhost kernel: mptbase: ioc0: LogInfo(0x31080000): Originator={PL}, Code={SATA NCQ Fail All Commands After Error}, SubCode(0x0000) cb_idx mptscsih_io_done
Oct 16 09:56:50 localhost kernel: LSI Debug log info 31080000 for channel 0 id 0
Oct 16 09:56:50 localhost kernel: sd 6:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 16 09:56:50 localhost kernel: sd 6:0:0:0: [sda] Sense Key : Medium Error [current]
Oct 16 09:56:50 localhost kernel: Info fld=0x4d59fc8
Oct 16 09:56:50 localhost kernel: sd 6:0:0:0: [sda] Add. Sense: Unrecovered read error
Oct 16 09:56:50 localhost kernel: sd 6:0:0:0: [sda] CDB: Read(10): 28 00 04 d5 9f c8 00 00 08 00
Oct 16 09:56:50 localhost kernel: end_request: critical medium error, dev sda, sector 81108936
Who know how to fix? Thank you!
Input/output error indicates that you system cannot read the file. Your log indicates that the hard drive is failing. Reinstall yum through RPM if you must, but ultimately backup your critical data and salvage the storage array.
I am trying to boot Fedora 20 with serial output,so I modify the boot command line with:
menuentry 'Fedora (3.18.0) 20 (Heisenbug)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-0-rescue-690525b7662a4bbca483ccdfdac3f6dc-advanced-d27ee4d5-522c-48e8-abc5-73b42bd81ae4' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 86088439-feab-4ac8-9cca-792414d9fff0
else
search --no-floppy --fs-uuid --set=root 86088439-feab-4ac8-9cca-792414d9fff0
fi
linuxefi /vmlinuz-3.18.0 root=UUID=d27ee4d5-522c-48e8-abc5-73b42bd81ae4 ro text no_console_suspend hpet=disable console=ttyS0,115200 console=tty0
initrdefi /initramfs-3.18.0.img
}
And the serial output seemed to stop at:
'a start job is running for Show Plymouth Boot Screen',
and did not go on.
and here are the journalctl message:
Jan 06 19:02:13 localhost.localdomain systemd[1]: Mounted /boot.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Mounting /boot/efi...
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Activation of DM RAID sets.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Encrypted Volumes.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Reached target Encrypted Volumes.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Mounted /boot/efi.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Local File Systems.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Reached target Local File Systems.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Mark the need to relabel after reboot.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Reconfigure the system on administrator request.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Relabel all filesystems, if necessary.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Recreate Volatile Files and Directories...
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Security Auditing Service...
Jan 06 19:02:13 localhost.localdomain auditd[468]: Error - audit support not in kernel
Jan 06 19:02:13 localhost.localdomain auditd[468]: Cannot open netlink audit socket
Jan 06 19:02:13 localhost.localdomain auditd[468]: The audit daemon is exiting.
Jan 06 19:02:13 localhost.localdomain auditctl[469]: Error - audit support not in kernel
Jan 06 19:02:13 localhost.localdomain auditctl[469]: Error - audit support not in kernel
Jan 06 19:02:13 localhost.localdomain auditctl[469]: Cannot open netlink audit socket
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Recreate Volatile Files and Directories.
Jan 06 19:02:13 localhost.localdomain systemd[1]: auditd.service: main process exited, code=exited, status=1/FAILURE
Jan 06 19:02:13 localhost.localdomain systemd[1]: Failed to start Security Auditing Service.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Unit auditd.service entered failed state.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Jan 06 19:02:13 localhost.localdomain systemd-journal[394]: Permanent journal is using 24.0M (max 601.3M, leaving 902.0M of free 2.1G, current limit 601.3M).
Jan 06 19:02:13 localhost.localdomain systemd-journal[394]: Time spent on flushing to /var is 172.987ms for 1168 entries.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Jan 06 19:02:13 localhost.localdomain systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Jan 06 19:02:17 localhost.localdomain kernel: random: nonblocking pool is initialized
finally I solved this problem by appending:
console=tty console=ttyS0,115200n8
rather than:
console=tty0 console=ttyS0,115200
in boot command line
I don't know why,but it works,thanks god.