Hi all,

in case someone has the same problem I wanted to post this piece of info. Especially if you want to use it as a headless server this will hopefully save you some time


My Raspberry Pi 3 is running Slackware ARM 14.2 nicely, but I had one problem that was driving me nuts. WLAN (Wifi) worked smoothly, but as soon as I wanted to ssh into the Raspberry Pi something went wrong. Setting the output to verbose, it indicated that the connection went fine, but after successfully logging in nothing happened: The Terminal window seemed totally frozen. After several searches I finally found a thread that showed me that others have the same problem and that there is a simple solution.

It seems to be a general Raspberry Pi 3 problem and not restricted to any peticular distribution. If you want to take a closer look yourself see page 4 of https://www.raspberrypi.org/forums/v...8631&start=75#


There are at least three options to overcome the problem if you don't want to use eth0 interface or use an external USB wifi dongle:

- Connect to it using ipv6. Use

to scan for ipv6 addresses of devices on your local wifi network and
to connect to the Raspberry Pi. Obviously you should replace "pi", the address itself and the interface name (wlan0) according to your needs and the nmap output.


- Second choice: Edit your /etc/ssh/sshd_config and add the line:
This should ssh let leave the ToS number at zero instead of setting it to 0x10.

- Third: You could create an iptables rule. In the above linked thread a suggestion using ipv4 is:
According to the linked thread there might also occur problems with ntp on other systems that have the same cause. In my case on Slackware ARM 14.2 ntp worked nicely without changing anything, but in case you might experience an unchangeable system time (although ntp seems to succeed) you should look at https://www.raspberrypi.org/forums/v...?f=28&t=141454 where an iptables based solution is shown.

Thanks for the post, every bit of info helps document for others down the road.

I've been running my rpi3 with slackware current hard float since about August and have not had any ssh issues using wifi.

Good info. I've not had any issues like this on the RPi3 but then I'm not using the onboard WNIC. I have a cheap RealTek USB wireless adapter which doesn't give me any problems at all. I find the onboard WNIC to be a little lacking in range and consistency, plus it tends to drop the wireless connection quite often.

@Pentux:
+1
"flaky" compared to my many Realtek-s

@Serovec: thank-s

You're welcome,
Of interest: The R_Pi3 seem to have it's wireless tandem just slapped on. At least it's my impression: my Motorola phone's integrated wifi outperform that of Pi, no chance the 2005 Defy had better chips on disposal than 2014 Raspberry foundation?
IMO they're cheap:
Banana Pi M1 is both better ingeneered and part-sourced compared to R_Pi B2
Save the community, R_Pi has little to offer, and Banana now has Slackware supporting it, in --current, and that counts some, eh?

Whether or not the Raspberry Pi has little, or a lot, to offer is entirely subjective.

The one thing that the Raspberry Pi has going for it is the number of units that have been manufactured and its user-base. Quite a significantly higher number than Banana Pi. Which is down to the fact that the Raspberry Pi caught the public´s attention, more so than any other ARM based device before it, with a marketing strategy which focused on ¨education in schools¨. I mean, in this modern, and perpetually evolving, technological age conscientious parents were falling over each other to (literally) buy into the Raspberry Pi concept. It worked! Not many people cared about how limited the RPi was at the time. I know of half a dozen parents who bought one to prompt their kid(s) into becoming the next ´Albert Einstein´ which ended up in the trash, broken and/or unused.

Contrary to popular hearsay, I´m not a great fan of the RPi. My interest in the device is promoting the use of Slackware ARM, pretty much exclusively. For sure, there are more sophisticated, revolutionary, and pioneering ARM devices out there, but not with as large a user-base. It´s a crying shame there isn´t half as many Slackware ARM users on the Rpi as there are Raspbian users.

Raspberry is sub standard
@Exaga
You hit the nail on it's head
However I wouldn't agree the RPi has an overly humongous community. At least not one that counts, has merit or adds value:
Yes, You noted the involuntary members, then the wrong purchases (got two B1 where i needed the BPi M1 i bought later and subbed the one) and those members who just use the shipped images -the majority.
Compared to what's left, Banana has significant community, there are mostly power users, contributing members and developers, sadly fragmented to several Debians, Arch and apparently Slackware.

The raspberry really didnt add to the community except hype, I personally count it as another English fraud, FWIW. Kind of part of their folclore.
I back this claim with other devices out there having non proprietary kernel and are entirely open, as the Beagle SBCs, Open MOKO and the Arduino, all non England based.
Yet Raspberry stole the show.
And the silly price, advertised as low (9 pounds for zero) yet unobtainable below $22 anywhere?
Im sure this has a name in customers protection jargon

The day the Raspberry foundation published an open and free patch for the vanilla kernel, that builds and boots, I will reconsider my opinion. Or wait until they hit mainline proper. As long as there is an dedicated developer bound to kook the boot up, the Raspberry is as broken as an iPhone.
And it's about time someone says this out loud?

Get an Banana Pi, they have far better power supply
Get an BeagleBone, they have far better driver support
Get an Arduino, It has an mature IDE and tons of examples with thousands of active members
Just avoid the Raspberry, The early models where obsolete when designed already, the Pi3 is broken out of the box thermally and has sub standard WiFi that gets outperformed by even mediocre USB devices.
And usses micro USB for 2A rated power demand? Really? Yes really.
I could go on, but i believe my point is clear?

Yet millions of users have bought one and are using it. Sub-standard or not! I'm quite sure the same would be said of Slackware by many in the Debian and Ubuntu community. Slackware is often viewed as a decrepit and obsolete OS and, as ignorant and misinformed as that premise may be, it's one reason why people aren't taking the opportunity to install and run it.

The number of RPi users alone eclipses all other ARM based communities. The rest of your opinion is somewhat personal so I'll leave it there.

You only have to look at the number of RPi 'clones' to see how much it has contributed to society and the ARM device scene. You can't blame the RPi Foundation for structuring itself and marketing their products in the way that they have done and continue to do so, because it works so well. Maybe beyond their wildest dreams when you consider the RPi Foundation first planned to only make 10,000 units. Compare that figure with the many millions of RPis they have sold to date.

I have an Orange Pi Plus which is destined for some serious hard labour once H3 support reaches the mainline kernel. I'll even buy an Orange Pi Plus 2 at that time!

If you use the RPi3 for desktop and general multimedia purposes there's no thermal issue. It's only when you start to work it hard that it gets too hot and tends to crash, like when you're compiling for long periods. I've put a heatsink and fan on the SOC to keep it cool because I do a hell of a lot of compiling on the RPi3. I also own quite a few different RPi versions and would never advise users to avoid them. I'd much rather, wholeheartedly, encourage them to run Slackware ARM and put my efforts into helping people overcome any problems they might face while doing so!

Your point is very clear, in that if you look hard and long enough for faults (as with anything) you will surely find them.

You pretty much made a point by toning my rant down.

Stil I regret for not taking a Banana Pi M1 when I bought the Raspberries
Yes they can run Slackware, but they are plain silly compared to the like priced Bananas.
And I cant feel but being cheated about.

I will post, however any cool project I make with them, as time permits.

Regarding running Slackware on Raspberries, better hurry, as the next release won't support any older than the Pi3

FWIW
(is there an emoji for beating a dead horse?)