Raspberry3B+ Wifi

lambo69 · 04-26-2021, 04:29 AM

Hello,

i freshly installed Slackware-Arm (-current, 32 bit). After installation, wifi does not show. In the previous installation (which i accidently completely messed up, therefore a fresh install) with -current on that RPi, it worked. Now, wifi-device doesn't show.

Code:

root@xxx:~> ls /var/log/packages|grep sarpi
kernel-headers-sarpi3-5.10.31-armv7-1_slackcurrent_20Apr21_sp1
kernel-modules-sarpi3-5.10.31-armv7-1_slackcurrent_20Apr21_sp1
kernel_sarpi3-5.10.31-armv7-1_slackcurrent_20Apr21_sp1
sarpi3-boot-firmware-armv7-1_slackcurrent_20Apr21_sp1
sarpi3-hacks-3.0-armv7-1_slackcurrent_20Apr21_sp1

The deprecated rpi3-entry is not available in config.txt, wifi-device is not disabled

Code:

root@xxx:~> cat /boot/config.txt|grep wifi
#dtoverlay=disable-wifi

In the previous installation, i had a udev-rule for wifi:

Code:

root@xxx:~> cat /etc/udev/rules.d/70-persistent-net.rules

# net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b8:27:eb:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

# USB device 0x0424:0xec00 (usb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b8:27:eb:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Now, this rule doesn't seem to match. It doesn't make a difference, if this rule is present or not.

Try to find the device:

Code:

root@xxx:~> lsusb
Bus 001 Device 004: ID 1058:25a3 Western Digital Technologies, Inc. Elements Desktop (WDBWLG)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@xxx:~> rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

root@xxx:~> find /sys -name *rfkill*
/sys/devices/platform/soc/3f201000.serial/serial0/serial0-0/bluetooth/hci0/rfkill0
/sys/devices/virtual/misc/rfkill
/sys/class/misc/rfkill
/sys/class/rfkill
/sys/class/rfkill/rfkill0
/sys/module/rfkill

root@xxx:~> cat /sys/class/rfkill/rfkill0/name
hci0

Shouldn't rfkill show two devices (bluetooth and wifi)?

The module loads:

Code:

root@xxx:~> modprobe brcmfmac
root@xxx:~> lsmod|grep brcmfmac
brcmfmac              335872  0
brcmutil               24576  1 brcmfmac
cfg80211              782336  1 brcmfmac

root@xxx:~> dmesg|grep brcmfmac
[    6.896927] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    6.904593] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.911366] usbcore: registered new interface driver brcmfmac
[    7.228829] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    7.327922] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed

In another Thread, someone suggested to get firmware from a debian-package. I tried, without success.

Code:

root@xxx:~> ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device

Has anyone an idea?

floppy_stuttgart · 04-27-2021, 07:04 AM

google "brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed"

Quote:

DISABLE_OOB=on

in /boot/cmdline.txt?
https://github.com/armbian/build/com...3d73990e3c77e9

Downgrade of the linux-firmware package ?
https://github.com/raspberrypi/linux/issues/4145

my guess for now (I dont use Slackware on my PIs and they have nomore Wifi..)

lambo69 · 04-29-2021, 02:26 AM

Thanks for your input. Unfortunately it didn't help.

With the original firmware i get:

Code:

root@xxx:~> dmesg |grep brcm
[    6.730801] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    6.744942] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.750797] usbcore: registered new interface driver brcmfmac
[    6.947208] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch
[    6.956829] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.998448] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[    7.070200] Modules linked in: uas brcmfmac brcmutil hci_uart btbcm sha256_generic cfg80211 bcm2835_codec(C) bcm2835_isp(C) bluetooth bcm2835_v4l2(C) v4l2_mem2mem ecdh_generic bcm2835_mmal_vchiq(C) ecc videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops rfkill videobuf2_v4l2 videobuf2_common videodev raspberrypi_hwmon mc vc_sm_cma(C) uio_pdrv_genirq uio fixed
[    7.094954] Workqueue: brcmf_wq/mmc1:0001:1 brcmf_sdio_dataworker [brcmfmac]
[    7.157010] [<8013cf9c>] (queue_work_on) from [<7f2e6e60>] (brcmf_fw_crashed+0x5c/0x64 [brcmfmac])
[    7.169942] [<7f2e6e04>] (brcmf_fw_crashed [brcmfmac]) from [<7f2dfb88>] (brcmf_sdio_dataworker+0x694/0x2674 [brcmfmac])
[    7.179832] [<7f2df4f4>] (brcmf_sdio_dataworker [brcmfmac]) from [<8013d45c>] (process_one_work+0x220/0x57c)
[    9.514413] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[    9.523691] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[    9.526754] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66
[    9.526779] ieee80211 phy0: brcmf_c_process_clm_blob: clmload (4733 byte file) failed (-110)
[   12.074409] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[   12.083245] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[   12.086162] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66
[   12.086184] ieee80211 phy0: brcmf_c_process_clm_blob: get clmload_status failed (-110)
[   12.091303] ieee80211 phy0: brcmf_c_preinit_dcmds: download CLM blob file failed, -5
[   12.096592] ieee80211 phy0: brcmf_bus_started: failed: -5
[   12.099247] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5
[   12.138066] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed
[   12.141232] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[   12.144089] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66

I got firmware from Centos:

Code:

curl --location https://github.com/raspberrypi/firmware/raw/master/boot/bcm2710-rpi-3-b.dtb > /boot/bcm2710-rpi-3-b.dtb
curl --location https://github.com/RPi-Distro/firmware-nonfree/raw/54bab3d6a6d43239c71d26464e6e10e5067ffea7/brcm80211/brcm/brcmfmac43430-sdio.bin > /lib/firmware/brcm/brcmfmac43430-sdio.bin
curl --location https://github.com/RPi-Distro/firmware-nonfree/raw/54bab3d6a6d43239c71d26464e6e10e5067ffea7/brcm80211/brcm/brcmfmac43430-sdio.txt > /lib/firmware/brcm/brcmfmac43430-sdio.txt

...rebootet and

Code:

root@xxx:~> dmesg |grep brcm
[    6.823771] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    6.849313] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.855683] usbcore: registered new interface driver brcmfmac
[    6.941003] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch
[    7.104198] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    7.127318] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[    7.197218] Modules linked in: uas brcmfmac brcmutil sha256_generic cfg80211 hci_uart btbcm bluetooth bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem ecdh_generic ecc bcm2835_mmal_vchiq(C) rfkill videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common raspberrypi_hwmon videodev mc vc_sm_cma(C) uio_pdrv_genirq uio fixed
[    7.220443] Workqueue: brcmf_wq/mmc1:0001:1 brcmf_sdio_dataworker [brcmfmac]
[    7.282661] [<8013cf9c>] (queue_work_on) from [<7f2bbe60>] (brcmf_fw_crashed+0x5c/0x64 [brcmfmac])
[    7.289262] [<7f2bbe04>] (brcmf_fw_crashed [brcmfmac]) from [<7f2b4b88>] (brcmf_sdio_dataworker+0x694/0x2674 [brcmfmac])
[    7.307531] [<7f2b44f4>] (brcmf_sdio_dataworker [brcmfmac]) from [<8013d45c>] (process_one_work+0x220/0x57c)
[    9.674415] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[    9.683692] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[    9.686762] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66
[    9.686787] ieee80211 phy0: brcmf_c_process_clm_blob: clmload (4733 byte file) failed (-110)
[   12.234475] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[   12.243295] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[   12.246214] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66
[   12.246236] ieee80211 phy0: brcmf_c_process_clm_blob: get clmload_status failed (-110)
[   12.251357] ieee80211 phy0: brcmf_c_preinit_dcmds: download CLM blob file failed, -5
[   12.256659] ieee80211 phy0: brcmf_bus_started: failed: -5
[   12.259323] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5
[   12.298063] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed
[   12.301225] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[   12.304083] brcmfmac: dongle trap info: type 0xc @ epc 0x0001ec66

The interesting thing, with both versions:

Quote:

[ 6.956829] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 6.998448] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
...
[ 12.246236] ieee80211 phy0: brcmf_c_process_clm_blob: get clmload_status failed (-110)
[ 12.251357] ieee80211 phy0: brcmf_c_preinit_dcmds: download CLM blob file failed, -5
[ 12.256659] ieee80211 phy0: brcmf_bus_started: failed: -5
[ 12.259323] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5
[ 12.298063] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed
[ 12.301225] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle

Has anyone a hint, where else to look? Unfortunately i'm not familiar enough to interpret.

Exaga · 04-29-2021, 03:02 AM

Quote:

Originally Posted by lambo69

Hello,

i freshly installed Slackware-Arm (-current, 32 bit). After installation, wifi does not show. In the previous installation (which i accidently completely messed up, therefore a fresh install) with -current on that RPi, it worked. Now, wifi-device doesn't show.

Has anyone an idea?

Hi lambo,

[EDIT] Before doing anything, make sure your Slackware ARM system is up-to-date with the latest available packages.
If you're using SARPi pkgs then download and install them from here: https://sarpi.penthux.net/index.php?p=downloads
'slackpkg' can facilitate the installation of multiple pkgs if you're not doing it manually.

Really not sure what the problem is here for you. Usually I have wireless and Bluetooth disabled but after reading about your issue(s) I did some testing on my RPi4 running Slackware ARM current. I'm using the latest SARPi pkgs and usually work entirely from command line...

Code:

root@torq:~# uname -a
Linux torq 5.10.32-v7l-sarpi4 #2 SMP Wed Apr 28 18:10:46 BST 2021 armv7l BCM2711 GNU/Linux

First I checked to see if the modules were loaded...

Code:

root@torq:~# lsmod
Module                  Size  Used by
bnep                   20480  2
8021q                  32768  0
garp                   16384  1 8021q
stp                    16384  1 garp
llc                    16384  2 garp,stp
ipv6                  499712  20
dm_mod                131072  0
rtc_ds1307             32768  0
regmap_i2c             16384  1 rtc_ds1307
btsdio                 16384  0
bluetooth             421888  8 btsdio,bnep
ecdh_generic           16384  1 bluetooth
ecc                    36864  1 ecdh_generic
brcmfmac              335872  0
brcmutil               24576  1 brcmfmac
sha256_generic         16384  0
bcm2835_codec          40960  0
cfg80211              782336  1 brcmfmac
bcm2835_v4l2           49152  0
videobuf2_vmalloc      16384  1 bcm2835_v4l2
v4l2_mem2mem           36864  1 bcm2835_codec
rfkill                 32768  3 bluetooth,cfg80211
bcm2835_isp            32768  0
bcm2835_mmal_vchiq     28672  3 bcm2835_isp,bcm2835_codec,bcm2835_v4l2
videobuf2_dma_contig    20480  2 bcm2835_isp,bcm2835_codec
raspberrypi_hwmon      16384  0
videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_vmalloc
vc_sm_cma              32768  2 bcm2835_isp,bcm2835_mmal_vchiq
videobuf2_v4l2         32768  4 bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem
i2c_bcm2835            16384  0
videobuf2_common       61440  5 bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
videodev              258048  6 bcm2835_isp,bcm2835_codec,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2
mc                     45056  6 bcm2835_isp,bcm2835_codec,videobuf2_common,videodev,v4l2_mem2mem,videobuf2_v4l2
rpivid_mem             16384  0
uio_pdrv_genirq        16384  0
uio                    20480  1 uio_pdrv_genirq
nvmem_rmem             16384  0

That looks OK. Then I checked to see if the wlan0 interface was accessible...

Code:

root@torq:~# iwconfig wlan0
wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

root@torq:~# ifconfig wlan0
wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether dc:a6:32:67:c4:2c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Then I performed a scan to see if my wireless Internet connection was found...

Code:

root@torq:~# iwlist wlan0 scan
wlan0     Interface doesn't support scanning : Network is down

root@torq:~# ip link show wlan0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether dc:a6:32:67:c4:2c brd ff:ff:ff:ff:ff:ff

Ooops! Forgot to bring up the wlan0 interface... no carrier!

Code:

root@torq:~# ifconfig wlan0 up
root@torq:~# iwlist wlan0 scan

wlan0     Scan completed :
          Cell 01 - Address: 98:FC:11:70:E3:23
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=70/70  Signal level=-32 dBm
                    Encryption key:on
                    ESSID:"SARPI2G"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000

<- results in a long list of available wireless connections, including the one I expected to see ->

I usually invoke 'networkmanager' to connect wirelessly for testing. It's quick and easy compared to doing it manually. The procedure is very well covered on this page: https://sarpi.penthux.net/index.php?p=wireless-nic

Code:

root@torq:~# nmtui
NetworkManager is not running.
root@torq:~# chmod +x /etc/rc.d/rc.networkmanager
root@torq:~# /etc/rc.d/rc.networkmanager start
Starting NetworkManager daemon:  /usr/sbin/NetworkManager
root@torq:~# nmtui

Once I've finished setting up the wireless connection with 'networkmanager'...

Code:

root@torq:~# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.216  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::da27:ed6f:ff3c:6e28  prefixlen 64  scopeid 0x20<link>
        ether dc:a6:32:67:c4:2c  txqueuelen 1000  (Ethernet)
        RX packets 3  bytes 1180 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 15  bytes 2445 (2.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

All working as expected.

If you are having trouble then I'd advise getting rid of everything that already exists on the system and starting over. So...

Code:

root@torq:~# ifconfig wlan0 down
root@torq:~# rmmod brcmfmac

Also, remove any rules for wireless cards that may exist in the following file

Code:

root@torq:/# nano -w /etc/udev/rules.d/70-persistent-net.rules

Then reboot and start over from scratch. That's what I usually do when I face problems such as yours.

https://sarpi.penthux.net/index.php?p=wireless-nic should help you to be successful. If not get back to me.

lambo69 · 04-29-2021, 04:44 AM

Thank you for the hint with the new software, but nothing has changed...

Code:

root@xxx:~> ls /var/log/packages |grep sarpi
kernel-headers-sarpi3-5.10.32-armv7-1_slackcurrent_28Apr21_sp1
kernel-modules-sarpi3-5.10.32-armv7-1_slackcurrent_28Apr21_sp1
kernel_sarpi3-5.10.32-armv7-1_slackcurrent_28Apr21_sp1
sarpi3-boot-firmware-armv7-1_slackcurrent_28Apr21_sp1
sarpi3-hacks-3.0-armv7-1_slackcurrent_28Apr21_sp1

root@xxx:~> uname -a
Linux xxx.lan 5.10.32-v7-sarpi3 #2 SMP Wed Apr 28 18:11:13 BST 2021 armv7l BCM2835 GNU/Linux

root@xxx:~> lsmod |grep brcm
brcmfmac              331776  0
brcmutil               24576  1 brcmfmac
cfg80211              782336  1 brcmfmac

root@xxx:~> iwconfig wlan0
wlan0     No such device

By now, i think it's a hardware-failure. Somewhere else, i have another RPi3 and i'm going to try that sdcard there, during the weekend. I will report.

business_kid · 04-29-2021, 05:06 AM

I hit that fault on a Pi 4. Firmware?
I download the Debian one and things started to work. I tried going back to the original, and that worked also

. Now either work.

You get the Debian stuff in RPi OS. They have patched the .bin file, and it's noticeably larger.

Exaga · 04-29-2021, 06:18 AM

Quote:

Originally Posted by lambo69

Thank you for the hint with the new software, but nothing has changed...

By now, i think it's a hardware-failure. Somewhere else, i have another RPi3 and i'm going to try that sdcard there, during the weekend. I will report.

In the past I have come across issues where the wireless interface refused to initialise. It's usually driver/firmware related or due to a mis-configuration. That's why I've advised to make sure the system is fully up-to-date before trying to "fix" it. There's been occasions where users have had terminal problems simply because certain installed pkgs were older versions. I don't mean just the SARPi system pkgs, but Slackware ARM pkgs too. There's been other times when the [upstream] firmware has been the culprit.

Due to the problems you are facing I've double-checked for my own peace of mind and wasted some time testing the latest SARPi pkgs on the RPi3B+. Sorry to say the onboard wireless NIC is working as expected on this device for me. So, hmmm... cannot imagine what's causing the problems on your setup. Except this I noticed from your logs...

Code:

root@xxx:~> dmesg |grep brcm
[    6.744942] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.750797] usbcore: registered new interface driver brcmfmac
[    6.947208] Bluetooth: hci0: BCM43430A1 'brcm/BCM43430A1.hcd' Patch
[    6.956829] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.998448] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed

Now, the above for the RPi3B (not plus) might be all well and good. For the RPi3B+ is looks like this on mine...

Code:

root@jook:~# dmesg | grep brcmfmac43
[    6.635943] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    6.996760] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

BCM43430 is used on the RPi3B - BCM43455 is used on the Rpi3B+. I know there's an open and ongoing issue on https://github.com/raspberrypi/linux/issues/2453 regarding these problems but, all I can say is that on my Slackware ARM current setup on the RPi3B+ there are no issues with wireless connectivity.

However, although having an onboard WNIC should be easy and convenient it often isn't, and can be much the opposite. Due to the perpetual problems that some users face with onboard wireless connectivity on the RPi devices I frequently advise an additional USB wireless adapter is what should be considered. I have various USB wireless adapters for testing, ranging from the "cheap and chearful" bargain-basement offerings to the overtly and unmerited expensive garbage available. What I have found works best is whatever Slackware ARM is happy with. That often means devices which are either already supported by the OS and/or ones where the software has been done well. Two of the best USB wireless adapters I have found to work flawlessly with Slackware ARM are (don't laugh - but please feel free if you can't help it) the RaLink RT5370 and RealTek rtl88x2bu - the former just works without any fuss but it is quite old/slow and the latter has firmware/drivers that you can build yourself and is one of the fastest I've used. These are the benefits and strengths that these wireless adapters offer for the end-user.

Sorry I cannot be of more help but the crux of your problem(s) is not clear to me. It's going to take some time and testing to find out exactly what's going on with your RPi3B+ setup in order to fix it, if indeed it can be resolved at all easily. First and foremost make sure everything is fully up-to-date on the system. That's the golden rule.