Slackware - ARMThis forum is for the discussion of Slackware ARM.
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.
I'm not sure what the exact filename of the firmware would be for your system, I only know it for the 400. If you can determine exactly which firmware *should* be loaded, try looking for duplicate filenames in /lib/firmware.
I've just done a complete re-install of slarm64 (on a new sd card!), and that troublesome ap6256 folder is definitely there again! I'm not sure where its coming from, as it certainly isn't in the kernel-firmware package! I will need to move it out of the way as part of my (ongoing) setting up!
My new install does not have that /opt/vc/bin/vcmailbox file. Can't remember where I must have got it from - perhaps form the same location as the bluetoothResetFirmware.sh script? I'll have to go back and have a look...
louigi, clear something up. In various posts, you’ve mentioned SlackwareARM 14.2 and Sarpi and RPi 4.
But those aren’t meant to go together. You should only be installing -current on RPi 4, otherwise - problems!
So , do you have -current or 14.2 on your Pi4?
I don’t understand it enough to explain why you’ll have problems. I’m going by the instructions on the Sarpi website.
Getting that right doesn’t eliminate the BT problems, though.
TKS
I have kernel form current and userland from 14.2, there is no official kernel for the RPi4 running 14.2 so that's just a workaround since I don't like to run current.
The kernel does offer hardfloat but the userland will never require it so it's ok to use the current kernel on softfloat userland.
Actually the only problem I have is bluetooth, everything else is working fine, ethernet, wifi, audio, X ... I even compiled the kernel with Exaga's bt config.
I don't think it's because I'm doing this workaround to run 14.2 on my RPi4 ... but I have 2 more spare uSD ... I can try current on one of them and see how it goes.
And besides that I think Exaga himself is having the same problem on current.
I have also a RPI4 running current and impossible to make PI Bluetooth work !
I have also tested many things without success !
When I plug a USB Bluetooth adapter, everything works perfectly ! But impossible to use the onboard Bluetooth adapter
Quote:
Originally Posted by louigi600
I have kernel form current and userland from 14.2, there is no official kernel for the RPi4 running 14.2 so that's just a workaround since I don't like to run current.
The kernel does offer hardfloat but the userland will never require it so it's ok to use the current kernel on softfloat userland.
Actually the only problem I have is bluetooth, everything else is working fine, ethernet, wifi, audio, X ... I even compiled the kernel with Exaga's bt config.
I don't think it's because I'm doing this workaround to run 14.2 on my RPi4 ... but I have 2 more spare uSD ... I can try current on one of them and see how it goes.
And besides that I think Exaga himself is having the same problem on current.
Desiderius: This is a firmware issue! I have a Pi 400 which is different from the 4, but some of the fixes I used on the 400 apply. The only one that may not is patching Bluez, and even one of those patches is probably a good idea. Have a look here: https://www.linuxquestions.org/quest...-a-4175689669/
The main points are: 1) Replace the /lib/firmware/brcm folder with the one from a recent Raspbian. 2) If your system has a /lib/firmware/ap6256 folder, move it out of the way (I put it in /root/tmp). Don't just delete it, in case you need it back!
This should make your adapter appear! If it still won't bind, try patching Bluez - but I believe this is only necessary for the 400.
The reason for moving the ap6256 folder is that it contains files with the same names as some in the brcm folder. Being higher up the "pecking order", it gets loaded first, so the updates to brcm become ineffective! Moving the ap6256 folder out of the way allows the correct firmware from the brcm folder to load.
That is my experience anyway! It certainly works on the 400.
Guys I have copied from PRiOS with working onboard bluetooth (on the very same RPi4):
the entire /lib/firmware and /etc/firmware is linked to /lib/firmware.
kernel and modules
boot firmware
The only thing that is left over is the renaming txt file I renamed ... I will remove that and see if it's any better.
I will take with me one of my old bt dongles and see if they work with the same setup.
Where can I download the Raspbian /lib/firmware/brcm ?
Desiderius
Quote:
Originally Posted by pchristy
Desiderius: This is a firmware issue! I have a Pi 400 which is different from the 4, but some of the fixes I used on the 400 apply. The only one that may not is patching Bluez, and even one of those patches is probably a good idea. Have a look here: https://www.linuxquestions.org/quest...-a-4175689669/
The main points are: 1) Replace the /lib/firmware/brcm folder with the one from a recent Raspbian. 2) If your system has a /lib/firmware/ap6256 folder, move it out of the way (I put it in /root/tmp). Don't just delete it, in case you need it back!
This should make your adapter appear! If it still won't bind, try patching Bluez - but I believe this is only necessary for the 400.
The reason for moving the ap6256 folder is that it contains files with the same names as some in the brcm folder. Being higher up the "pecking order", it gets loaded first, so the updates to brcm become ineffective! Moving the ap6256 folder out of the way allows the correct firmware from the brcm folder to load.
That is my experience anyway! It certainly works on the 400.
Click on the appropriate version for your system, and it will take you to a second page where you can find the hacks package.
I'm not sure if Exaga uses the "pure" Raspbian files, or if he tweaks them somewhat. I've been using the pure Raspbian ones, which are a bit more effort to obtain, but I know they work!
I will try to extract it from the Raspian image since actually I have the files from the Exaga sarpi-hacks package ( since I use SARPI to install Slackware ) and it does not work.
Yes, please let us know! I'm afraid I only have a 400, so my experience is not necessarily applicable to other Pis! But from your description of your problem, it sounds the same as mine!
Guys I have copied from PRiOS with working onboard bluetooth (on the very same RPi4):
the entire /lib/firmware and /etc/firmware is linked to /lib/firmware.
kernel and modules
boot firmware
The only thing that is left over is the renaming txt file I renamed ... I will remove that and see if it's any better.
I will take with me one of my old bt dongles and see if they work with the same setup.
Not sure if RPiOS uses some stuff out of /opt/vc to make the bluetooth work but on 14.2 I can't do much about it because I can't find a softfloat version of that stuff.
Concerning the firmware now even the renamd txt fie was removed and still can't see the onboard BT device.
I have some interesting updates that also span to a little OT from this post.
I recently treated myself with a new 2Gb ram RPi4 instead of the stingy 1Gb I'd usually buy (the old one will become a NAS).
Code:
Hardware : BCM2711
Revision : b03114
Serial : 100000009dc116e9
Model : Raspberry Pi 4 Model B Rev 1.4
with SARPi4 kernel build from Jan 2021 (v 5.10.11) on the above device usb does not work at all ... but seems to be fine with latest 5.10.14.
No change at all regarding BT on this device even with latest SARPi kernel and firmware.
I set up a multiboot uSD so that the 14.2 userland on it will boot from both RPi4 and RPi0 ... so I can also report that BT on the RPi0 is in the same state as the RPi4
First I have looked for an ap6256 folder on the RPI : no ap6256 folder !
In /lib/firmware I have renamed the "brcm" folder to "old_brcm" and I have put the "brcm" folder extracted from the actual Raspberry PI OS image.
Look for an ap6256 folder : no !
Chown root:root to brcm and reboot !
No Bluetooth icon in the task bar and when asking KDE for Bluetooth adapters, the answer is "No adapter available" !
To be sure, I have plugged an USB Bluetooth stick and the icon appears in the task bar and KDE sees the USB adapter !
Quote:
Originally Posted by pchristy
Desiderius: This is a firmware issue! I have a Pi 400 which is different from the 4, but some of the fixes I used on the 400 apply. The only one that may not is patching Bluez, and even one of those patches is probably a good idea. Have a look here: https://www.linuxquestions.org/quest...-a-4175689669/
The main points are: 1) Replace the /lib/firmware/brcm folder with the one from a recent Raspbian. 2) If your system has a /lib/firmware/ap6256 folder, move it out of the way (I put it in /root/tmp). Don't just delete it, in case you need it back!
This should make your adapter appear! If it still won't bind, try patching Bluez - but I believe this is only necessary for the 400.
The reason for moving the ap6256 folder is that it contains files with the same names as some in the brcm folder. Being higher up the "pecking order", it gets loaded first, so the updates to brcm become ineffective! Moving the ap6256 folder out of the way allows the correct firmware from the brcm folder to load.
That is my experience anyway! It certainly works on the 400.
tried both SARPi hack /lib/firmware and RPiOS /lib/firmware
tried both SARPi boot firmware RPiOS boot firmware
tried latest SARPi kernel (5.10.14) and RPiOS kernel (5.4.83)
Onbpard bluetooth does work if I boot RPiOS but not with any of the above combinations with slackwareARM 14.2.
USB bluetooth dongles work fine.
I tried on the below RPi models :
Code:
Hardware : BCM2711
Revision : a03111
Serial : 1000000091328354
Model : Raspberry Pi 4 Model B Rev 1.1
Hardware : BCM2711
Revision : b03114
Serial : 100000009dc116e9
Model : Raspberry Pi 4 Model B Rev 1.4
Hardware : BCM2835
Revision : 9000c1
Serial : 000000009b4bd2c0
#this is a RPi0W
Does RPiOS send some vc command to switch on the onboard BT, something with rfkill: they must do something which is not driver/firmware related (I tried with their kernel and firmware).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
