[SOLVED] Slackware on Cubox pro

mike_booth76 · 02-13-2015, 01:16 AM

I treated myself to one of these for Christmas hoping to run slackware ( as I've been using that for years and like it) I've finished up with Gentoo as it seems to almost worl out of the box.

With Slackware I've failed to get wireless networking going after many frustrating hours. There is little or no documentation for the Slackware port.Fatdog seem to have lost interest.

I know the wireless hardware is OK as it works on Gentoo.

Can anyone help me get this going on Slack?

Mike

louigi600 · 02-13-2015, 03:29 AM

I don't have the hardware so I can't give you any direct help ... but probably the quickest way to get it working in Slackware is to use kernel, modules and firmware from Gentoo.

justwantin · 02-13-2015, 04:18 PM

Have you tried using iwconfig and then wicd (from /extras)? That's what I use on my pi's. Seems this easiest to do, at least for me. If you already have entries in /etc/rc.d/rc.inet1.conf you will have to remove them for wicd to work.

Quote:

.... Fatdog seem to have lost interest.

Maybe he has over the past few weeks but the downloads on the website are dated 17Jan15 and he states clearly on the home page/second paragraph

Quote:

From this guide you are able to install Slackware ARM 14.1, or 14.0, on a Raspberry Pi

Configuration is another matter.

If you run iwconfig you will find out if your wireless device is recognised.

Code:

root@shed-2:~# iwconfig
wlan0     IEEE 802.11bg  ESSID:"gerrygarcia"  Nickname:"rtl_wifi"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 94:44:52:0C:B4:39   
          Bit Rate:54 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=98/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

You can see the output from one of my pi's above that already has been configured for wireless. I used the command [iwconfig essid gerrygarcia] to set up the ESSID, then configured the rest using wicd-curses to do the rest of the setup (see attachment below).

One might question using wicd but it allows me to run anything dependent on a wireless connection after I have a wireless connection using a post connection script

Code:

bash-4.3# cat /etc/wicd/scripts/postconnect/start_logger 
$!/bin/bash

/usr/sbin/sntp -s pool.ntp.org 

mjpg_streamer -i "/usr/lib/input_uvc.so -d /dev/video0  -r 640x480 -f 20" -o "/usr/lib/output_http.so -p 8090 -w /var/mjpg-www" &

/etc/rc.d/rc.weather_logger start

Exaga · 02-14-2015, 03:21 AM

Quote:

Originally Posted by mike_booth76

There is little or no documentation for the Slackware port. Fatdog seem to have lost interest.

I´ll assume you are referring to http://humbo.fatdog.eu - Slackware ARM on the Hummingboard.

I was working on this project solo to begin with, so progress was very slow. However, the plan was for a few of us to obtain different SolidRun devices so we could work collectively, and more efficiently, to bring Slackware ARM to the HummingBoard/Cubox-i. This unfortunately hasn´t happened yet. Free time is also a commodity in high demand, yet short supply. We currently have our hands on several different projects and Slackware ARM on the HummingBoard is not high on the grand list of priorities.

It´s not that FatDog have lost interest. Far from it.

Exaga · 02-14-2015, 03:35 AM

Quote:

Originally Posted by justwantin

Maybe he has over the past few weeks but the downloads on the website are dated 17Jan15 and he states clearly on the home page/second paragraph ...

That would be the Slackware ARM on a Raspberry Pi website.

We´re currently working on the Raspberry Pi 2 installer. It´s business as usual on the Raspberry Pi (1).

mike_booth76 · 02-16-2015, 11:34 PM

Thanks for the advice guys. As it turned out the problem was with the Broadcom firmware.

I eventually copied all the BRCM f/ware files from a working opensuse image and hey presto.

Maybe someone else will find this helpful.

Rgds

Mike

aihaike · 09-06-2016, 12:02 PM

Quote:

Originally Posted by mike_booth76

Thanks for the advice guys. As it turned out the problem was with the Broadcom firmware.

I eventually copied all the BRCM f/ware files from a working opensuse image and hey presto.

Maybe someone else will find this helpful.

Rgds

Mike

Hey Mike,

I don't have acces to any opensuse image.
Where else can I get those files?
Would you please provide the names?
Thank you!

Eric.

mike_booth76 · 09-07-2016, 02:52 AM

hi. The files were brcmfmac4330-sdio.bin and brcmfmac4330

Good Luck

Mike