I guess one it for WLAN and WPAN and the other only for WLAN support.
No need anything permission just moving to /lib/firmware. Just do not forget to delete the rps file after burning…
1 Like
Yes, HKS on and BT enabled. With BT disabled, I don’t get the last output line from dmesg.
Which log file should I provide?
To start troubleshooting reburn the new firmware to Redpine if it fails on this then go downgrade then upgrade of versions. Then Reboot.
Ok, now I get;
[ 23.336635] redpine_91x: Operating mode 13 is only supported prior to firmware 2.x
[ 23.342835] redpine_91x: rsi_probe: ***** 9116 Module *****
[ 23.343627] redpine_91x: redpine_hal_device_init: oper_mode = 13, coex_mode = 2
[ 23.351778] redpine_91x: Received Board Version Number: 10
[ 23.357493] redpine_91x: rsi_load_firmware: Loading file RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 23.357616] redpine_91x: rsi_load_firmware: Failed to open file RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 23.369710] redpine_91x: ***** Loaded Firmware *****
[ 28.387273] redpine_91x: ================================================
[ 28.387301] redpine_91x: ================ RSI Version Info ==============
[ 28.387304] redpine_91x: ================================================
[ 28.387308] redpine_91x: FW Version : 1.2.20.0
[ 28.387422] redpine_91x: RSI FW Version : 0000.1.2.0.0502
[ 28.387429] redpine_91x: Driver Version : RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
[ 28.387433] redpine_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
[ 28.387438] redpine_91x: Firmware file : RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 28.387442] redpine_91x: ================================================
[ 28.402291] redpine_91x: rsi_send_bt_reg_params: Sending BT reg frame
[ 28.402780] redpine_91x: HCI module init done...
[ 28.405345] redpine_91x: RSI HCI DEVICE "hci0" open
[ 28.443772] redpine_91x: RSI `hci0' flush
[ 28.443805] redpine_91x: RSI HCI DEVICE "hci0" closed
[ 28.443810] redpine_91x: rsi_hci_close: device `hci0' not running
[ 28.500825] redpine_91x: <==== Interface UP ====>
[ 28.500939] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 28.500945] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates....
[ 28.531505] redpine_91x: <==== Interface DOWN ====>
[ 28.533929] redpine_91x: <==== Interface UP ====>
[ 28.533985] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 28.533992] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates....
[ 32.527185] redpine_91x: <==== Interface DOWN ====>
[ 32.530934] redpine_91x: <==== Interface UP ====>
[ 32.530993] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 32.531000] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates....
[ 36.340749] redpine_91x: EAPOL 4 confirm
1 Like
just wanted to confirm i have bluetooth stuttering as well with the non free driver
1 Like
Sorry if this was stated already but the impression I’m getting is that these firmware updates will be entirely up to us to perform, they will not be rolled out in OS updates?
Which one Driver or Firmware?
You tell me is it just the firmware upgrades we are responsible for or both firmware and driver?
For Firmware peoples is responsable to perform, the Driver in the Operating System, the newer driver for Redpine is not shipped because there is a issue for licenses. At this point i recommend do not do anything until the new driver arrive, u will notified from this thread.
3 Likes
I’m running kernel 6.1.0-1-librem5 and here is the dmesg dump am I running the right firmware?
purism@pureos:~$ sudo dmesg | grep redpine
[sudo] password for purism:
[ 11.665848] redpine_91x: rsi_probe: ***** 9116 Module *****
[ 11.666391] redpine_91x: redpine_hal_device_init: oper_mode = 5, coex_mode = 2
[ 11.667618] redpine_91x: Received Board Version Number: 10
[ 11.668798] redpine_91x: rsi_load_firmware: Loading file RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 13.201203] redpine_91x: FW Length = 329216 bytes
[ 13.201231] redpine_91x: ================================================
[ 13.201235] redpine_91x: ================ RSI Version Info ==============
[ 13.201239] redpine_91x: ================================================
[ 13.201242] redpine_91x: FW Version : 2.1.0.0
[ 13.201247] redpine_91x: RSI FW Version: 1610.2.1.ab.ffbf
[ 13.201253] redpine_91x: Driver Version: RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
[ 13.201256] redpine_91x: Operating mode: 5 [Wi-Fi STA + BT EDR]
[ 13.201261] redpine_91x: Firmware file: RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 13.201265] redpine_91x: ================================================
[ 13.385728] redpine_91x: *** Flash CRC passed ***
[ 13.395023] redpine_91x: ***** Loaded Firmware *****
[ 18.403931] redpine_91x: ================================================
[ 18.403948] redpine_91x: ================ RSI Version Info ==============
[ 18.403952] redpine_91x: ================================================
[ 18.403955] redpine_91x: FW Version : 1.2.0.16
[ 18.403960] redpine_91x: RSI FW Version: 1610.1.2.ab.ffbf
[ 18.403966] redpine_91x: Driver Version: RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
[ 18.403969] redpine_91x: Operating mode: 5 [Wi-Fi STA + BT EDR]
[ 18.403974] redpine_91x: Firmware file: RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 18.403977] redpine_91x: ================================================
[ 18.412816] redpine_91x: rsi_send_bt_reg_params: Sending BT reg frame
[ 18.413354] redpine_91x: HCI module init done…
[ 18.413490] redpine_91x: RSI HCI DEVICE “hci0” open
[ 18.492335] redpine_91x: <==== Interface UP ====>
[ 18.492426] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 18.492432] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates…
[ 18.519969] redpine_91x: <==== Interface DOWN ====>
[ 18.525976] redpine_91x: <==== Interface UP ====>
[ 18.526115] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 18.526148] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates…
[ 22.423835] redpine_91x: <==== Interface DOWN ====>
[ 22.427951] redpine_91x: <==== Interface UP ====>
[ 22.427995] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[ 22.428003] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates…
[ 26.198787] redpine_91x: EAPOL 4 confirm
I’ve noticed a stutter in Bluetooth as well with my new L5 with the SparkLAN card.
I was running the local radio station in a tab in Firefox, it sounded great ~until~ the screen switched off - then it began to stutter,
i guess it is because the inactive _mode slow down the cpu, to save batt, at the same time Firefox it is a big monster eating resources. Try to streaming a song with a music player to see if happening same issue?
I never use Firefox in L5, instead Epiphany.
Just tried it with Lollypop and it seems better, with the occasional stutter but not the continual fluttering I experienced with Firefox. So it does seem somewhat CPU bound(?) regardless
First you need to make that the firmware for Redpine it up to date, this will reduce stutering.
The Inactive Mode when the monitor is off may cause stutering ATM, maybe fix later.
Let me explain: that happen because Purism try build the best security gnu+lnx phone in the world, but there are not parts truly optimized for mobile to make the dream gnu+lnx phone, so Purism utilized mobile part(not optimized) to finish the best gnu phone, so that mean that the phone will be big power/heat hungry, so Purism it doing an fancy work to save the battery everywhere in the device by reducing cpu or whatever it needed. So that is why exist issue and stutering everywhere, but Purism will FIX all stutering, issues eventually by performing optimizes, part replaces(sparklan),and accelerations. The security level of librem 5 make power hungry and heat too, by using many parts by separate.
A truly gnu+lnx phone like Librem 5 is working better and better with the ages, while opensources android type devices get worse and worse by ages.
2 Likes