Librem 5 received and inital reaction

[    5.396914] Bluetooth: Core ver 2.22
[    5.397034] Bluetooth: HCI device and connection manager initialized
[    5.397051] Bluetooth: HCI socket layer initialized
[    5.397059] Bluetooth: L2CAP socket layer initialized
[    5.397074] Bluetooth: SCO socket layer initialized
[    8.116647] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.116686] Bluetooth: BNEP socket layer initialized
purism@pureos:~$

Nothing that looks out of the ordinary I suppose? But here’s any fail or error from
dmesg

purism@pureos:~$ sudo dmesg | grep -i fail
[    3.870937] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[    4.943230] imx-sdma 302c0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    4.946034] imx-sdma 30bd0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    5.166630] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.166642] cfg80211: failed to load regulatory.db
[    5.516886] RSI-SDIO WLAN mmc1:fffd:1: Direct firmware load for RS9116_NLINK_WLAN_BT_IMAGE.rps failed with error -2
[    5.516900] redpine_91x: rsi_load_firmware: Failed to open file RS9116_NLINK_WLAN_BT_IMAGE.rps
[   16.865772] redpine_91x: redpine_set_clr_tx_intention,357: Wait event failed
[   16.865809] redpine_91x: rsi_tx_scheduler_thread,623:  Failed to get tx_access
[  759.737388] g_multi gadget: userspace failed to provide iSerialNumber
purism@pureos:~$

and

purism@pureos:~$ sudo dmesg | grep -i error
[    4.288271] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[    4.943230] imx-sdma 302c0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    4.946034] imx-sdma 30bd0000.sdma: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    5.166630] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.336867] wm8962 2-001a: ASoC: error at soc_component_read_no_lock on wm8962.2-001a: -16
[    5.347978] wm8962 2-001a: ASoC: error at soc_component_read_no_lock on wm8962.2-001a: -16
[    5.516886] RSI-SDIO WLAN mmc1:fffd:1: Direct firmware load for RS9116_NLINK_WLAN_BT_IMAGE.rps failed with error -2
[  792.932888] edt_ft5x06 2-0038: Unable to fetch data, error: -6
purism@pureos:~$

Thanks.

Did you try checking if the antennas are properly seated on the WiFi module?

I did I here’s a pic. I did mention in my correspondance with support via email that they felt really really loose/flimsy. I mean -I barely touched it and it popped off. So I carefully popped it back on and uhh. yea. Here’s a pic:

I’ll check again now though.

Also:

purism@pureos:~$ sudo mmcli -m any
  -----------------------------
  General  |         dbus path: /org/freedesktop/ModemManager1/Modem/0
           |         device id: 2af0ed38a023bf40b592aa26f1b17c60446066c8
  -----------------------------
  Hardware |      manufacturer: QUALCOMM INCORPORATED
           |             model: 0
           | firmware revision: MPSS.JO.2.0.2.c1.1-00032-9607_GENNS_PACK-1  1  [Feb 25 2019 01:00:00]
           |    carrier config: default
           |      h/w revision: 10000
           |         supported: gsm-umts, lte
           |           current: gsm-umts, lte
           |      equipment id: 863974040054340
  -----------------------------
  System   |            device: /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
           |           drivers: qmi_wwan, option1
           |            plugin: broadmobi
           |      primary port: cdc-wdm0
           |             ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at),
           |                    ttyUSB3 (at), wwan0 (net)
  -----------------------------
  Status   |             state: failed
           |     failed reason: sim-missing
           |       power state: on
           |    signal quality: 0% (cached)
  -----------------------------
  Modes    |         supported: allowed: 2g; preferred: none
           |                    allowed: 3g; preferred: none
           |                    allowed: 4g; preferred: none
           |                    allowed: 2g, 3g; preferred: 3g
           |                    allowed: 2g, 3g; preferred: 2g
           |                    allowed: 2g, 4g; preferred: 4g
           |                    allowed: 2g, 4g; preferred: 2g
           |                    allowed: 3g, 4g; preferred: 4g
           |                    allowed: 3g, 4g; preferred: 3g
           |                    allowed: 2g, 3g, 4g; preferred: 4g
           |                    allowed: 2g, 3g, 4g; preferred: 3g
           |                    allowed: 2g, 3g, 4g; preferred: 2g
           |           current: allowed: any; preferred: none
  -----------------------------
  Bands    |         supported: pcs, g850, utran-4, utran-5, utran-2, eutran-2, eutran-3,
           |                    eutran-4, eutran-5, eutran-12, eutran-13, eutran-17, eutran-25,
           |                    eutran-26, eutran-41, eutran-66
  -----------------------------
  IP       |         supported: ipv4, ipv6, ipv4v6
purism@pureos:~$

I don’t have a sim it today. Last one I had in there somehow died? Maybe scratched I don’t know. Waiting on new sim.

It definitely does not feel like its seating in there tightly.

That’s the best pic I can get. But yea like I mentioned. I was told to open it up and check them before. I told them that it felt loose and flimsy(the cable connection) And now it looks like the cable on the right is much much more lose than the one on the left. *The cable should almost “snap” into place. And from day one when I took this out of the box a few days ago I was tasked to check the cables and right then I new that cable on the right was going to be an issue.

*lastly, I am confident tearing apart my own computers and pi’s and other IOTs but I do NOT feel good about poking around this device. If it was $100 phone I’ve have this thing apart and replace those cables yesterday. But I do not want to be responsible for this. This should not be fixed by me. I think that is reasonable correct? Software wise? Yes lets do it -tell me what to edit/compile/run etc. But I am not touching this hardware. And to be clear and honest I obviously don’t quite grock the setup on this device yet. So I just want to be clear that I am not a hardware engineer lol. Just trying to make it through the day is all.

5 Likes

My BT worked for several months, but at one point (after an update, I believe), it started misbehaving. I can enable it, and the emblem appears in the notifications area, but it doesn’t seem to scan for devices. Also, sometimes the emblem is not in sync with the Settings app (toggles itself off, but the emblem stays in the notifications for a while). It worked fine for most functionality in my first few months of ownership.

I don’t really have a need for BT on the L5 at present, so I haven’t worked on getting to the cause. I just expect that it will get straightened out with an update at some point.

2 Likes

Thanks. I expect these things to happen as far as the software but I had a feeling this was a hardware issue from day one. * I could be wrong. I’d like to be wrong but these antenna cables are buggin me out man! I’m prob wrong about it being hardware. I don’t know why I keep going there.

I guess that your BlueTooth it fine on hardware it is just that is not working at the moment. My bluetooth it doesn’t work for me either, but worked before. I believe that the BT it going be fixed on some point, Purism developers is busy fixing other bugs. I hope Byzantium will be launched soon and that you enjoy this wonderful L5 machine more.

What’s not working with your bluetooth? Is the service running? Is the Bluetooth device found?(lsusb |grep -i blue) is the Bluetooth process found in the system monitor yet? For me The only thing that I see is that the Bluetooth option in the GUI is grayed out and not responsive. bluetoothctl runs fine but its not finding the control or any controller. So while I’d like to believe its just a driver issue I won’t exactly count out the hardware. Like I had mentioned -that one coaxil antenna cable does not have my trust. We’ll see. Still I am interested in knowing what exactly is not working with your Bluetooth. Thanks.

Just wanted to add some /proc info. Its Friday night I know haha.

purism@pureos:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=c000000000000 0

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="bd718xx-pwrkey"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.0.auto/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="pwm-vibrator"
P: Phys=
S: Sysfs=/devices/platform/vibrator/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=200001
B: FF=107030000 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="30370000.snvs:snvs-powerkey"
P: Phys=snvs-pwrkey/input0
S: Sysfs=/devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="EP0700M09"
P: Phys=
S: Sysfs=/devices/platform/soc@0/30800000.bus/30a40000.i2c/i2c-2/2-0038/input/input4
U: Uniq=
H: Handlers=event4 mouse0
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="WM8962 Beep Generator"
P: Phys=2-001a
S: Sysfs=/devices/platform/soc@0/30800000.bus/30a40000.i2c/i2c-2/2-001a/input/input6
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="wm8962 Headphones"
P: Phys=ALSA
S: Sysfs=/devices/platform/sound/sound/card1/input5
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=4

purism@pureos:~$

I’m wondering if this is a Debian 11/upstream issue. I just clean installed Debian 11 on my work laptop (intel WiFi /Bluetooth) and I can’t get Bluetooth working that has worked fine for the last 5 years on the laptop just fine. Similar looking error in dmesg, just different driver of course. It also broke suspend. Debian freezes are the worst :stuck_out_tongue_winking_eye:

1 Like

I got a kernel update today it is the version Linux5.13.14, so after this update my Bluetooth is working again on app settings. : )
I guess that the trick to get working the BT is reboot with BT enabled on settings.

3 Likes

Yea no dice. I think I got that last light. Still Bluetooth is unresponsive no matter what with the same issues listed above. And in fact my WiFi is hit and miss I’ve noticed. Sometimes it connects but most times I have to reboot and then it will connect. And then it will hang on one bar. Sometimes it says I have 3-4 bars but fails to resolve hostnames in any ping or any internet connection via ssh/web-browser/curl/etc. So at this point its as useful as an ink-less pen. So Glad your Bluetooth is working. Still looking for some solid help from support on getting mine to work. Its literally the ONLY thing getting in my way. of being satisfied.-

Hey @carlosgonz do you have a LibremUSA or the regular Librem? Just curious on the difference between wifi/bluetooth modules. Thanks.

I have Librem 5 Evergreen regular, i wish to have a Librem 5 USA because i believe this has a 4 GBs RAM.
There is a bug on Gnome stack related to refresh BT, so go to settings app then enable bluetooth so next close the settings app, then go again to bluetooth settings, then should be working for you.
@dos do you have a solutions soon to fix the refresh BT page on Gnome settings. Please ?

Ah thanks. Yea that will not work for me. I CANNOT enable or disable bluetooth from the GUI/app settings. The settings for Bluetooth is not responsive at all. So no matter what I try that GUI/App settings for Bluetooth is grayed out and does not respond at all. I’m not sure what to say here. The Bluetooth settings has not been responsive since opening this out of the box. The service is running when checking with systemctl from the terminal and I can restart it from there but that does nothing. The device is not found in /proc or lsusb or hcitool dev or hciconfig -a sudo lshw | grep -i blue and because the Bluetooth device is not showing up in ANY search I will still say this could be hardware problem. * The Wifi almost always takes minutes to connect to the network and then when it does its at 1 bar and is not giving me any connectivity from like ssh. All I am saying is that the WiFi is also very very flaky.

1 Like

Maybe some BT libs is broken. Why not flashing your device to Byzantium? Prepare your computer to install uuu then learn how put the L5 on flash mode and flashing… to Byzantium. If the BT issue still there after byzantium, mmm may be a hardware problems.
Purism It has had a lot of problems with the BT card and the driver. I think Purism will release another wifi-BT card to solve all the problems it has, and maybe wifi 6 and suspend mode on the newer card. :slight_smile:

1 Like

What makes you think that? As far as I know, the Librem 5 USA has 3 GB ram, just like the regular Librem 5. Check here: https://puri.sm/products/librem-5-usa/ (“Hardware Specifications: Librem 5 USA” near bottom of that page)

3 Likes

I readed on some Purism post that L5 USA will come with 4GB of RAM to justify a little the high price but maybe i wrong.
Can @joeybronzoni confirm this?

1 Like

Yup, @Skalman is correct. USA comes with 3GB RAM. But you are correct @carlosgonz it I did still get to pay the high price. LOL. I kid I kid. I know what this is about. I honestly believe the work done on this and other Linux phones is going to be a huge step in the right direction for the future of tech. Whether or not people see it yet I will stand by my theory. Linux will take us into the future, not windows, not apple, but maybe TempleOS will get resurrected haha(It is an amazing project). Either way though… I want my Bluetooth to get sorted out. At the very least I want confirmation that its not a hardware issue. That would ease some of the pain.

4 Likes