slarm64This forum is for the discussion of slarm64.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK, I've upgraded the kernel - no noticeable difference. I can confirm that now I have sound over hdmi, it is working!
I'm attaching the dmesg file for 5.17.4 with the exaga bluetooth fix. Bluetooth is working, audio is working over hdmi, but no wifi.
One other thing I've found is that if I set inittab to 4 (launch into sddm), dmesg fills up with the following message:
Code:
[ 200.166481] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 200.166541] vc4-drm gpu: [drm] dumb: 280212kb BOs (32)
[ 200.169316] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 200.169376] vc4-drm gpu: [drm] dumb: 280172kb BOs (31)
This repeats continuously as long as X is running. It doesn't show in the attached dmesg because I ran it from runlevel 3. I think this has only started since the uEnv.txt location was moved - at least, I'd not noticed it before.
OK, I've upgraded the kernel - no noticeable difference. I can confirm that now I have sound over hdmi, it is working!
I'm attaching the dmesg file for 5.17.4 with the exaga bluetooth fix. Bluetooth is working, audio is working over hdmi, but no wifi.
One other thing I've found is that if I set inittab to 4 (launch into sddm), dmesg fills up with the following message:
Code:
[ 200.166481] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 200.166541] vc4-drm gpu: [drm] dumb: 280212kb BOs (32)
[ 200.169316] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 200.169376] vc4-drm gpu: [drm] dumb: 280172kb BOs (31)
This repeats continuously as long as X is running. It doesn't show in the attached dmesg because I ran it from runlevel 3. I think this has only started since the uEnv.txt location was moved - at least, I'd not noticed it before.
--
Pete
CMA in kernel is set to CONFIG_CMA_SIZE_MBYTES=128
No WIFI due to firmware loading error
Code:
[ 5.583935] brcmfmac: F1 signature read @0x18000000=0x15294345
[ 5.588456] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 5.589055] usbcore: registered new interface driver brcmfmac
[ 5.619373] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
Yes, I had already done that. However, I did make one error. A while back, I blacklisted all the kernel stuff in /etc/slackpkg/blacklist so that kernel stuff wouldn't overwrite your kernel packages. Unfortunately, I must have been too late and there was an old kernel-firmware file still there. I removed it, re-installed your kernel-firmware package, but alas, no change:
Code:
$ ls /var/log/packages/kernel-*
/var/log/packages/kernel-bcm2711-5.17.4-aarch64-1mara
/var/log/packages/kernel-firmware-bcm2711-5.17.4-aarch64-1mara
/var/log/packages/kernel-headers-bcm2711-5.17.4-aarch64-1mara
/var/log/packages/kernel-modules-bcm2711-5.17.4-aarch64-1mara
/var/log/packages/kernel-source-5.14.0-noarch-1
/var/log/packages/kernel-source-bcm2711-5.17.4-noarch-1mara
$ dmesg | grep brcmfmac
[ 5.672848] brcmfmac: F1 signature read @0x18000000=0x15294345
[ 5.677406] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 5.678069] usbcore: registered new interface driver brcmfmac
[ 5.720479] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
[ 6.881672] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 7.897821] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
and still no wifi.
Quote:
CMA in kernel is set to CONFIG_CMA_SIZE_MBYTES=128
$ dmesg | grep brcmfmac
[ 5.863160] brcmfmac: F1 signature read @0x18000000=0x15294345
[ 5.867848] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 5.868447] usbcore: registered new interface driver brcmfmac
[ 5.902055] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
[ 6.100452] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 6.100520] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 6.111848] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: May 14 2020 17:26:08 version 7.84.17.1 (r871554) FWID 01-3d9e1d87
[ 12.595859] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 13.121093] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
I now have wifi showing as enabled in NetworkManager, but no networks showing. This might have something to do with that "power saving enabled" message. I will investigate!
I'm still getting those cma messages, though. Clutching at straws, I modified the config.txt file to
I'm still not getting anywhere with this, and its driving me nuts! However, I'm beginning to wonder if its a memory issue, as since I relocated the uEnv.txt location, some strange things have been happening...
1) I get this error repeating in dmesg:
Code:
53.622540] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 53.622674] vc4-drm gpu: [drm] dumb: 308960kb BOs (18)
2) I get odd crashes in KDE - trying to run systemsettings produces an instant segfault:
Code:
$ systemsettings
kf.kirigami: Failed to find a Kirigami platform plugin
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
kf.kirigami: Failed to find a Kirigami platform plugin
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:151:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ApplicationItem.qml:147:9: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Failed to create scanout resource
DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Failed to create scanout resource
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 2069
KCrash: Arguments: /usr/bin/systemsettings
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
[1]+ Stopped systemsettings
both of these seem to be complaining about being unable to allocate memory.
I've reinstalled the whole of kde, qt and NetworkManager, to no avail.
which accounts for all the neighbourhood wifi signals. In other words, the hardware is working!
Also:
Code:
rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But:
Code:
nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
wlan0 wifi unavailable --
lo loopback unmanaged --
Why is wifi showing as unavailable? Is it possible it is also suffering from memory allocation issues? I have googled this problem to death without success.
Ok, tried booting the kernel directly (as an aside, the reason it had stopped working was missing initrd. Copying uInitrd to initrd got kernel boot working again).
I've tried to adding a line "cma=512MG" to config txt and also appending it to the vc4 overlay:
Code:
dtoverlay=vc4-kms-v3d,cma-512
I've also tried the vc4pkms-v3d-pi4 overlay, but nothing has worked. Still getting the error message, and still no wifi.
One thought: If I'm booting the kernel directly, does uEnv.txt still get called? I thought it was part of uBoot? What was the original location for it? (I should have written that down!) Is it worth trying it back at its original location, now that I've got the kernel to boot directly again?
I'm going to call it a night at this point, as my eyes are starting to funny from staring at the monitor so long!
Thanks for your help!
UPDATE: Found the original address higher up this thread. Tried it, but no difference.
--
Pete
Last edited by pchristy; 04-24-2022 at 01:16 PM.
Reason: update
Yes, I use rc.inet1.conf on my desktop, but that's hardwired. I use NetworkManager on my laptop (Slackware64-15.0) without any issues, and I have had it working on the Pi400. The annoying thing is that all the tests (rfkill, iwlist, etc) say that it is there and available, but NetworkManager insists its NOT available. There are lots of reports of similar problems on Google, but none of the fixes I've found there have worked.
One other interesting thing, and one other question, if I may? When I fired up the machine today, the cma error messages had disappeared! I can only assume that a reboot wasn't enough to clear the old memory, and it needed a full shutdown - wait a while - and then restart to clear! (This is with "dtoverlay=vc4-kms-v3d,cma-512")
The other question is that since uEnv.txt is called by uBoot, how does this configuration get done when booting the kernel directly, without uBoot?
Oh, and one final thing: Probably the reason that "dtoverlay=enable-bt" didn't work is that I can find no such overlay on my machine! Where should it be?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
