Internal WiFi status?

[Username_012]

Didn't work, my PineTab 2 does not boot after installing this kernel. I will have to investigate further.

[Wilmeri]

I had success in being able to suspend without any hangs and the wifi on using the following.

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

Finally got it to work; needed to add some delay after wifi off.

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

And similar sleep for the shutdown. Thanks everyone!

Edit: sorry.. no. it does not always work

[mtomaschett]

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!

[pinewood]

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

[cringeops]

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.

[stevepaesani]

This process of developing a working WiFi driver/kernel module seems a bit strange to me.  Should it be more in collaboration with the Linux project and with a plain main board, not in a final form factor?
https://gitlab.com/TuxThePenguin0/bes2600

Wouldn't it be easier for someone to convince the original source code (  Bestechnic?, BES? ) to work with The Linux Foundation and get the code distributed with the Linux kernel releases.  Or work with Software Freedom Conservancy and release it fully under the GPL v2, which Segfaults's GitLab repo seemed to be working toward: https://gitlab.com/TuxThePenguin0/bes2600.  And figure out the proper channels and format to package and distribute the kernel module.

I gather another issue is the WiFi chipset really doesn't support the latest WiFi protocols... AC?

It is sad really, I have a PineBook Pro with Tow-Boot installed to the SPI and booting Debian Workstation (GNOME3) and it works well enough [even the WiFi and Bluetooth] to continue using a Linux Graphical Shell.  More RAM, touchscreen, and detachable keyboard would be nice upgrades.  these are much better form factors than the Raspberry Pi 5.  Yet, the Raspberry Pi 5 has a Broadcom BCM2712 quad-core Arm Cortex A76 processor and up to 8GB of RAM.

Oddly Starlabs and Fyde Linux tablets don't have this issue. So it would seem that there is no issue at all in getting cooperation from vendors.

May be more a matter of expecting or demanding drivers be written for free.

Maybe if the leaders of foss all did it 40 hours a week themselves it wouldn't be an issue. Though that's as unsustainable as Leopold's Congo operations at least it would be the people who initiated and are pushing the model that would be driven to abject poverty and their lives devalued and so right and just,

[Kevin Kofler]

As far as I know, the WiFi works just fine with current versions of the distributions targeting the PineTab2.

[wolfallein]

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.

Hi,
I have the latest arch kernel (6.14.7-danctnix1) and added the uart1 to the dtsi file as you suggested. It does not complain about the Input/output error anymore but bluetooth still do not work. I get this error:

Code:

Can't init device hci0: Invalid argument (22)

after I run: hciconfig hci0 up

Do you know an updated solution for bluetooth?