Quote:
Originally Posted by codeguy
I took the plunge. Upgrading the sarpi packages worked just fine. I'm now running
The sarpi-hacks fixed the wireless.
No lilo, or anything else, you just "upgradepkg *sarpi*.txz" and reboot.
I didn't do anything with rpi-update
|
Apologies for not getting back to you sooner but GTA 5 Online is quite demanding right now and taking up a hell of a lot of my time and attention at the moment. In fact, I took time out to reply to a few LQ posts but I really should be in Los Santos, raising Hell while gorging on Jaffa cakes! [Stocked up this morning!
]
The reason why sarpi-hacks includes this shizzle is because the SARPi Project flatly refuses to tinker with or modify Slackware ARM in any way to suit individual, collective, national, global, universal, cross-dimensional, or any other
extra-Slackwarial requirements. for public released software. That is; unless MoZes sanctions it. This [obviously] doesn't include Linux kernels or modules, or the README file, which we maul, mangle, and decimate, equally and accordingly to suit. The Slackware ARM source will remain as preserved and intact from the original as much as possible from the SARPi Project. We don't want to be remembering all the dirty hacks and misdemeanours we did to Slackware ARM when in a few months/years time someone will accuse MoZes of skulduggery when the culprit will have been SARPi. That's the kind of eventuality I can see happening if we ever choose to take that dubious path.
Why am I telling you this? Because [what some people don't appreciate is] in order to get things to work, sometimes you have to cut corners and take matters into your own hands, outside the scope of the operating system. With the Raspberry Pi, this is the kind of thing you need to resort to in order to get results. The Raspbian developers patch the system in order to get things to work on the RPi. I'm not sure what state Slackware ARM would be in if we resolved to do the same.
I've spent ~3 days working on the RPi 3/4 wireless and Bluetooth stuff in order to get it working for the convenience of Joe public, none of which I will
ever use myself, only for testing. I've managed to get wireless and Bluetooth working on
Slackware ARM -current without resorting to any jiggery-pokery or patching. The OS and kernel's configuration covers it adequately. However, the same cannot be said for Slackware ARM 14.2 which is proving somewhat troublesome. Right now I feel that I've spent more time than I would have liked to spend on trying to get it to work. As Slackware ARM 14.2 [i.e. soft float port] will become EOL on the release of Slackware 15, [
NB: I am on my god-forsaken knees praying for that day to arrive!] I don't have that much motivation towards nailing a solution for this Bluetooth problem on it. Especially because I won't be using it myself.
If you want wireless/Bluetooth on your RPi3/4 install Slackware ARM -current. When you do and if it's your first time, make sure you wear 2 pairs of pants because Slackware ARM -current is quite a bit quicker then what you'll be accustomed to on Slackware ARM 14.2.
[EDIT] in fact, if any of you would like to roll your sleeves up and get your hands dirty, and take on the Bluetooth issue on Slackware ARM 14.2 on the Rpi 3 and 4... feel free. If/when you are successful let me know your solution and I will include it in the SARPi stuff. Perhaps MoZes may be interested in such information too, you'd have to ask him.
