02-26-2024, 08:53 PM
03-01-2024, 01:42 PM
(02-24-2024, 12:57 PM)FortunateFowl Wrote: [ -> ]I had success in being able to suspend without any hangs and the wifi on using the following.Finally got it to work; needed to add some delay after wifi off.
Using your favorite text editor add the following text to the following two files
File at
Code:/usr/lib/systemd/system-sleep/wlan_stop.sh
Code:#!/bin/bash
if [ "$1" = "post" ]; then
echo "Post: $(date +%T)" >> /tmp/suspend
/usr/bin/nmcli radio wifi on
# /usr/sbin/modprobe bes2600
elif [ "$1" = "pre" ]; then
echo "Pre: $(date +%T)" >> /tmp/suspend
/usr/bin/nmcli radio wifi off
# /usr/sbin/modprobe -r bes2600
fi
exit 0
and again for shutdowns
add a file at
Code:/usr/lib/systemd/system-shutdown/wlan_stop.sh
Code:#!/bin/bash
# stops the wifi before shutting down, otherwise the current driver implementation hangs
/usr/bin/nmcli radio wifi off
exit 0
Code:
$ cd /usr/lib/systemd/system-sleep/
$ cat wifi.shutdown
#!/bin/bash
if [ "$1" == "pre" ]; then
echo "Pre $(date +%T)" >> /tmp/suspend
echo turning wifi off
/usr/bin/nmcli radio wifi off
/usr/bin/sleep 7
echo "Pre $(date +%T) done" >> /tmp/suspend
elif [ "$1" == "post" ]; then
echo "Post $(date +%T)" >> /tmp/suspend
/usr/bin/nmcli radio wifi on
fi
exit 0
Edit: sorry.. no. it does not always work
03-09-2024, 05:22 PM
I was able to enable wifi and bluetooth functionality by following the instructions by moobythegoldensock above, and I got the wifi to persist between reboots by creating service units as described by ninlith above.
I was not able, however, to get the bluetooth service to persist between boots. On reboot, checking the status of the bluetooth service indicates that it is inactive because:
Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth)
I have put the relevant commands from moobythegoldensock into a script which, when run, creates the bluetooth directory required by the service and enables bluetooth, but something is going wrong that bluetooth isn't getting loaded at boot time.
Anyone having similar prblems, or have any ideas that might point me toward a solution?
I am running arch:
Linux pinetab2 6.6.13-danctnix1-1-pinetab2 #1 SMP PREEMPT_DYNAMIC Mon, 22 Jan 2024 11:53:08 +0000 aarch64 GNU/Linux
Thanks!
I was not able, however, to get the bluetooth service to persist between boots. On reboot, checking the status of the bluetooth service indicates that it is inactive because:
Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth)
I have put the relevant commands from moobythegoldensock into a script which, when run, creates the bluetooth directory required by the service and enables bluetooth, but something is going wrong that bluetooth isn't getting loaded at boot time.
Anyone having similar prblems, or have any ideas that might point me toward a solution?
I am running arch:
Linux pinetab2 6.6.13-danctnix1-1-pinetab2 #1 SMP PREEMPT_DYNAMIC Mon, 22 Jan 2024 11:53:08 +0000 aarch64 GNU/Linux
Thanks!
04-30-2024, 12:07 PM
You aren't alone mtomaschett. I've got wifi working, but sadly I've never got bluetooth working.
I get to:
I get to:
Code:
#hciattch -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
Can't get port settings: Input/output error
Can't initialize device: Input/output error
05-04-2024, 08:00 AM
(04-30-2024, 12:07 PM)pinewood Wrote: [ -> ]You aren't alone mtomaschett. I've got wifi working, but sadly I've never got bluetooth working.
I get to:
Code:#hciattch -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
Can't get port settings: Input/output error
Can't initialize device: Input/output error
I'll commit the patch that fixes it to the mailing list. Meanwhile, you can fix it by adding the following to arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi and building the device-tree:
Code:
&uart1 {
pinctrl-names = "default";
pinctrl-0 = <&uart1m0_xfer &uart1m0_ctsn &uart1m0_rtsn>;
status = "okay";
uart-has-rtscts;
};
Bluetooth will "work" after that, but keep in mind that you won't be able to use mouses or keyboards, because they require encryption, which the generic UART driver does not support.