I'm just finishing installation on my Raspberry Pi. I have encountered a couple of problems that I haven't found an answer too. I did manage to work around them, but I would like to know how to resolve them for future reference.

1. During installation, I could never make the installation run from a thumb drive. The system would start as if it were installing but flash through to done in a couple of seconds. Of course nothing was actually installed. I worked around the problem by doing an ftp install.

2. After the system was installed and configured I ran slackpkg update, which worked fine. However, when I issued the slackpkg upgrade-all command I received an error about gpg not being correct. Updating the gpg key did not correct the error, even after selecting three different mirrors. I finally turned off gpg checking to complete the upgrade.

Now a question, will sbopkg work to install additional packages? LXDE comes to mind as the first thing I want. If not, how does one go about installing extra packages?

I have this gpg problem too, had to do like you said to make slackpkg work again, using current.
If what you want is just install a package installpkg, which is part o slackpkg will install a package for slackware.
If what you talking about is extra packages dependencies for LXDE for example, i cant answer it because i dont know, sorry.

sbopkg and sport, both of which draw from Slackbuilds.org, and build scripts from other Slackware users like AlienBOB, will work as expected on Slackware ARM as long as the software you are installing is being compiled from source code. In 95% of the cases, that is what SBo does, but there are some packages that just drop a binary onto your system; if that binary is not available for ARM, then the install will work but obviously the application will not run.

I guess my question was less than clear. What I would like to know is, can I use build scripts from slackbuilds.org or do I need slackbuilds specifically for slackware arm?

You beat me to the punch notKlaatu. Thank you.

No worries, interndan. I use sport on my raspberry pi('s) with great success. Upgrades and everything. It just works.

Did you update slackpkg first? I don't know how slackpkg actually works since I have never really used it, but it has a hard coded string containing the GPG key details - key name and email address. The recent updates last week contained a rebuild of slackpkg to contain the new key string:-


I don't know what happens if you just update the GPG key without changing slackpkg as well, since the key's email address and details are completely different from the previous key. Based on this thread and another in the main forum, my guess is that it doesn't work. I'd have mentioned to update slackpkg first in the Changelogs, but I'm not convinced slackpkg users really check the ChangeLog anyway ;-)

If you're running a release, there are new updates for 14.0 & 14.1 today. Presumably you've updated all of the previous packages (including slackpkg), can you see if slackpkg will successfully update to the new versions without having to override the GPG check?
If you're running -current then it'll have to wait a while since there won't be any updates there for a time.

Not sure what happened. Today slackpkg is working fine. I'm guessing what happened is when I ran the upgrades without gpg at the end I told it to over write config files with new configs. When I started slackpkg it told me no mirrors had been set. After setting mirror and running update everything worked. Gpg checking is on in new config.

Guilty here. I downgrade slackpkg to the 14.1 version then i upgrade it manually with the latest version from current, now it is working again

Here is another question, what is a good web browser to use on the Pi? I have LXDE installed and working so I would like to uninstall all the other DEs. Currently Konqueror is the only non text based browser installed. I would like to remove KDE as well.

I only used Firefox - it was useable on the Tegra20 (Trimslice) so should be reasonable on the Pi.
http://ftp.arm.slackware.com/slackwa...rent/packages/

The packages are a few months old now and are out of date - there's been many security fixes since I last built those.
I'll try updating them now but can't promise anything: Firefox often needs open heart surgery to get it building on ARM, and my instruments are usually hammers and chain saws ;-)

1 members found this post helpful.

Thanks, I'll give it a try. I was a worried that Firefox might be a little heavy for the Pi.

I've built 30.0 for -current (it probably still works on 14.1 at this moment in time) and tested it on the Trimslice. It's useable.

http://ftp.arm.slackware.com/slackwa...ackcurrent.txz

1 members found this post helpful.

I guess the next question on this topic is should I download and build drivers for the gpu? I didn't see them in the install instructions. I also should have pointed out that I followed the steps from fatdog.eu.

If I were in your boots I'd just get a hold of rpi-update and run that. The kernel and drivers will be optimised to run on a pi with latest improvements (if any). Fat Dog gives instructions on how to ugrade with rpi-update. I have never had any trouble using it.In the past (maybe 2012) I had used midori on slackware arm installed from packages built by Ponce. It was much quicker than FF.

I tried building Midori for a hard float install of slackware put together by Ahau but it required webkitgtk which I couldn't get to compile and each attempt was 24-36 hours before failure. After an install I access my pi's via ssh and so a browser is not a big priority.

FWIW Netsurf would be a perfect browser to use on a Pi but it was a chore to compile on this 32bit Salix box.