systemcarrotpt

I just posted a comment on an issue to git hub. There is one person there also reporting the error, he is indeed in kernel 5.4. Since its the same bug ill wait a couple to see how this develops because apparently it also happens on 5.4 Thanks for your help.

Hello Igor. Yes i use that wireless driver, im running hostapd as an access point along with a wifi adapter that uses that driver. So ill try to contact someone at the maintainer to let them know i have this problem. Thanks.

The driver is the one that comes with armbian out of the box. Its version is: # modinfo 88XXau filename: /lib/modules/4.4.213-rockchip64/kernel/drivers/net/wireless/rtl8812au/88XXau.ko version: v5.6.4.2_35491.20191025 Right now i dont have any update on apt-get, so i believe i have the latest from armbian repositories. I will try to look into that one on the link you gave me. Thank you for the help.

Hi all, I have been using a Rock64 with hostapd and a usb adapter that uses realtek drivers for a couple of months now. Recently, like a week or two, after what i believe was a kernel update i started getting random freezes in the board. As i use it "headless", when it happens the only way to get it back working is by power cycling it. This means that until today i had no logs of what was happening. Today although, i left my laptop on for a couple hours, with tail -f on kernel.log, messages and syslog. Attached in the file called logs.txt is what i managed to obtain from a terminated ssh session to the board. Im running Linux NetMan 4.4.213-rockchip64 #27 SMP Tue Apr 14 17:21:23 CEST 2020 aarch64 GNU/Linux. Anyone has any clues about it? Will there be a fix for this error? Should i downgrade the last update (i have a backup image) or try to update to kernel 5.4? Last time i tried a version 5 kernel i dont remember well but the board didnt boot or something. Thank you for the help. logs.txt armbianmonitor.txt

Well after some more digging i have come to a solution that solves my problem. In "/etc/udev/rules.d" i added the file "98-icybox.rules" and inside it i placed the following: ACTION=="add", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="5678", RUN+="/sbin/modprobe uas" RUN+="/bin/sh -c 'echo -n \"5-1:1.0\" > /sys/bus/usb/drivers/usbtouchscreen/unbind'" RUN+="/bin/sh -c 'echo -n \"5-1:1.0\" > /sys/bus/usb/drivers/uas/bind'" Now the Raid enclosure works right from boot.

I tried doing that in modprobe.conf adding blacklist usbtouchscreen, but that was ignored and the driver was still used after rebooting.

Hello, Were you able to set the right driver to the enclosure? I was able to get the RAID enclosure to be recognised by Armbian by unbinding the usbtouchscreen driver and then binding the uas driver to the enclosure. The device is still in two independent drives configuration (single mode), i didnt test any of the others but, i suppose that will not be a problem. In my case i done the following: Unbind: echo -n "5-1:1.0" > /sys/bus/usb/drivers/usbtouchscreen/unbind Confirm that nothing was binding to the device: tree /sys/bus/usb/devices/5-1:1.0 Bind the uas driver to the device. echo -n "5-1:1.0" > /sys/bus/usb/drivers/uas/bind After this the raid enclosure was available to use, doing a small speed test i got 40 MBps of a file transfer from the rock to my desktop. But now im facing another problem, if i do a reboot the enclosure is associated with the usbtouchsreen driver again. Do you or anyone have any idea on how i can specify a driver to be used for a device? Thanks