One subject which I have commented on often, but which in recent months I have gotten little or no new information about, was the stability of the WiFi chip-set on my laptop ‘Klystron’, which is driven by the kernel modules known as ‘RTL8732BE’.
Here is an earlier posting on this subject.
Since that posting, there have been 2 firmware updates to that laptop specifically. One, to version 1.159, and the next, to version 1.160.
What I found was that firmware version 1.159 actually seemed to make the WiFi very unstable again – a regression. But firmware version 1.160 seemed to make it stable again.
In the meantime, I have a script in directory
which is intended to deal with A Different Problem that laptop has, which was, that after resuming from sleep, the laptop system clock would seem to jump ahead exactly 68 hours. I had changed that script as an experiment. But now I have changed it back again, to:
#!/bin/bash # # fixing https://bbs.archlinux.org/viewtopic.php?id=173487 case "$1" in pre) date +%s > /tmp/suspend.log ;; post) was=`cat /tmp/suspend.log` now=`date +%s` # time shifts for 68 hours if [ $now -gt `expr $was + 244800` ]; then date -s "`date -R --date="68 hours ago"`" fi /bin/sh -c "sleep 20; /etc/init.d/nmbd restart; /etc/init.d/smbd restart" & ;; *) ;; esac
I often did suspect that problems which I had specifically associated with the kernel module, may not in fact stem from the kernel module. On my LAN, I use a router which is not owned by me, but rather by my ISP, and that router has numerous settings – as well as its own Firmware flashing – under the control of my ISP rather than under my direct control.
This router is still useful to me, because I subscribe to “Bell Fibe” and get to watch TV through it, in 1920x1080i resolution, which I could not do, if I was to try switching to a router owned by me.
But many of the problems which Klystron has on my WiFi, may all be policy issues with this router. Since I cannot get deep into the router settings, I am left guessing as to what router policies the laptop may not be abiding by.
But what this can do is lead to Samba problems specifically, which seem to mimic general WiFi connectivity issues, but which are not really examples of that.