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.
Did you get the fatdog installer to work? Mine wouldn't with it so thats why I had to do the minirootfs. But I found it easy enough to install slackpkg and use it to install stuff I needed.
Install Slackware ARM on a microSD card in a RPi1/2 and fully update the kernel and firmware, then take the sd card out and boot it in a RPi3? I haven't tested this myself but I know someone who's done this successfully.
According to the RPi Foundation, with their Device Tree overlays, it's possible to use the same image to boot multiple devices. So, it should be more than possible.
I have installed a Pi2 with slackware 14.1... runs GREAT...
recently bought 2 Pi3s and oddly enough noticed the Pi2 sd card would not start in the Pi3.... boo hoo..
after doing research as I could not find a non convoluted way to install directly on the Pi3 (SARPI3 anyone?)
I did found that I could compile and install "rpi-update" which updated the kernels on the sd card (as noted in a NON slackware like fashion) and HARK the old Pi2 sd would boot on both the Pi2 and the Pi3... EUREKA!!!
answer for me just image the old sd card from there and on to new SD card for the Pi3 re-size filesystems as needed and reconfigure for the new host... easy enough until new installer gets worked out everything working for me now that I have installed the firmware for the on-board wifi with the exception of BT, I have even cloned the rpi-kernel through GIT and compiled/installed the newest kernel for now 4.1.21-v7+
well I guess easy enough if you already have a Pi2... wonder if anyone can test by upgrading the kernel in the SARPI2 installer seeing that Pi2 will work with the same config.
I wrote that ... it used to have an issue with the way the fat partition was formatted ... but that should be fixed now.
The SD I built boots on both PI1 and PI2 so long as the have both kernels and modules.
I did found that I could compile and install "rpi-update" which updated the kernels on the sd card (as noted in a NON slackware like fashion) and HARK the old Pi2 sd would boot on both the Pi2 and the Pi3... EUREKA!!!
Besides enabling support for the RPi3, having up-to-date firmware will give you a noticeably increased performance on the RPi2 as well.
Ive always used rpi-update myself and never experienced any issues.
I just received a Pi3 and can't get the wifi to be recognized in "dmesg". From what I can tell, the firmware is in /lib/firmware/ so I'm at a loss for where to go from here.
Is there any interesting information in the kernel ring buffer ?
If there's too much junk in there remove the wifi module, clear the kernel ring buffer, reinsert the module and then examine it.
I think the wifi is on the usb bus too: does lsusb show the wifi card ?
Bus 001 Device 004: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I'll look into the .config for the kernel. There's a rumor that wifi wasn't enabled when it was compiled. If that's the case, I think I can recompile it and try to get it working. I just found this out maybe an hour ago.
In order to inspect the kernel ring buffer you can use "dmesg".
Looking at the output of lsusb I can't see the wifi card ... maybe it's on sdio. I don't have a Pi3 myself so I can only guess.
While googleing to find out more about the pi3's wifi I came across this: Raspberry Pi 3 Wifi Setup ... it's for raspbian but it might be interesting to read anyway.
The firmware is installed in /lib/firmware/brcm and is of the 43430 variety. Ubuntu for the Raspberry Pi will bring up the wifi but ARMslackware won't. Still can't get 'phy0' to be recognized by 'rfkill'.
The firmware is installed in /lib/firmware/brcm and is of the 43430 variety. Ubuntu for the Raspberry Pi will bring up the wifi but ARMslackware won't. Still can't get 'phy0' to be recognized by 'rfkill'.
Jim
Hi Jim
Where are you getting the firmware from? do you have the link to it on packages.ubuntu.com ?
I already include extra firmware for Realtek devices in the a/firmware package so could add some more if the licence is suitable.
I just "stole" it from an ubuntu image I'm also playing with. Another group and I are working on some satellite software that we're porting to Pi2 and Pi3 devices. If you'd like, I can send the ubuntu firmware directory as a tarball. Just let me know what you'd need and where to send it.
I just "stole" it from an ubuntu image I'm also playing with. Another group and I are working on some satellite software that we're porting to Pi2 and Pi3 devices. If you'd like, I can send the ubuntu firmware directory as a tarball. Just let me know what you'd need and where to send it.
Hi Jim
The firmware needs to be from a known externally referable source. Is it available from here?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.