Difference between revisions of "Software projects/OS/Slackware"

From Pandora Wiki
Jump to: navigation, search
(added Software projects/OS/Slackware/Advanced usage/Kernel)
m (new boards links)
 
(112 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
[[File:Lead_Photo_For_Software_projects-OS-Slackware0-49411322670714386.jpg|thumbnail|Slackware logo]]
 +
 
= Disclaimer =
 
= Disclaimer =
 
Hi, this is Linux-SWAT.
 
Hi, this is Linux-SWAT.
Line 8: Line 10:
 
Slackware ARM was formerly known as ARMedslack.
 
Slackware ARM was formerly known as ARMedslack.
  
The 14.0 release forum page is located here:
+
The 14.2 release forum page is located here:
http://boards.openpandora.org/index.php?/topic/9797-slackware-for-pandora-140/
+
https://pyra-handheld.com/boards/threads/slackware-for-pandora-14-2.80934/
  
 
The technical and -current forum page is located here:
 
The technical and -current forum page is located here:
http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/
+
https://pyra-handheld.com/boards/threads/slackware-inside-pandora.60258/
  
 
I'm the maintainer of this Slackware port, and you can find me here:
 
I'm the maintainer of this Slackware port, and you can find me here:
http://boards.openpandora.org/index.php?/user/1035-linux-swat/
+
https://pyra-handheld.com/boards/members/linux-swat.18403/
  
If you have questions, i suggest you to share it on the boards, not asking me privately.
+
If you have questions, I suggest you to share it on the boards, not asking me privately.
  
 
Important notes:
 
Important notes:
Line 31: Line 33:
 
I distribute this documentation under the GPL 3 license.
 
I distribute this documentation under the GPL 3 license.
 
http://www.gnu.org/licenses/gpl.html
 
http://www.gnu.org/licenses/gpl.html
 +
 +
= Features =
 +
 +
* Full hardware support
 +
* 12 window managers, including Xfce, Minimenu and Enlightenment DR17
 +
* KDE (512M RAM recommended), installed via internet in two commands
 +
* Pnd support
 +
* PNDmanager and PNDstore support
 +
* Armhf compatibility layer
 +
* Rebuilt optimized video player (MPlayer2)
 +
* Integrated YouTube player (SMTube, no Flash plugin needed)
 +
* Rebuilt optimized audio player (XMMS)
 +
* Integrated VOIP with Linphone
 +
* Integrated office suite, with AbiWord and Gnumeric
 +
* Integrated DisplayLink support
 +
* More than 400 Pandora-optimized pre-compiled packages (hosted @ openpandora.org)
 +
* Slapt-get and gslapt for easy installation of these pre-compiled packages
 +
* An automatized package building system (sbopkg)
 +
* Three optional standard firewall configs for eth0, usb0 and wlan0
 +
* Other optional firewall configs for routing/firewalling
 +
* Kernel recompilation made easy
 +
* Updates through official Slackware repository
 +
* The SL4P build system (hosted @ openpandora.org), which can be used to port any Linux/*NIX to Open Pandora
 +
* Official OP 3.X kernel + realtime kernel
 +
* Optimized Notaz's SDL
 +
* Bsp's c64-tools for the DSP
 +
* Glshim from Lunixbochs
 +
* Gl4es and SDL2 from ptitSeb
 +
* Gcc, make, perl, python2, python3, ruby, OpenJDK, SFML, etc.
  
 
= Helping this project =
 
= Helping this project =
 
* Please consider making a donation.
 
* Please consider making a donation.
 
* This will help the SL4P project, and also the whole Pandora community, as part of it funds pre-orders.
 
* This will help the SL4P project, and also the whole Pandora community, as part of it funds pre-orders.
* To do so, go to PayPal, log in and click on "Send Money". Donate to donation@openpandora.org and indicate in the PayPal comment field that you are donating for the Slackware project. Then PM me, so i will include you in my thx list ;^).
+
* To do so, go to PayPal, log in and click on "Send Money". Donate to donation@openpandora.org and indicate in the PayPal comment field that you are donating for the Slackware project. Then PM me, so I will include you in my thx list ;^).
  
 
= Older releases Wiki pages =
 
= Older releases Wiki pages =
* To keep this front page clean for the most recent release - 14.0 -, i moved previous versions elsewhere.
+
* To keep this front page clean for the most recent release - 14.2 -, I moved previous versions elsewhere.
 +
* The old page for the 14.1 release is located [http://pandorawiki.org/Software_projects/OS/Slackware-14.1 here.]
 +
* The old page for the 14.0 release is located [http://pandorawiki.org/Software_projects/OS/Slackware-14.0 here.]
 
* The old page for the 13.37 release is located [http://pandorawiki.org/Software_projects/OS/Slackware-13.37 here.]
 
* The old page for the 13.37 release is located [http://pandorawiki.org/Software_projects/OS/Slackware-13.37 here.]
 +
 +
= OS architecture =
 +
* 14.2 is the last and final ARMv5te, little endian, software float ("soft-float", "armel"), EABI.
 +
* 14.2 has the armhf compatibility layer, therefore can run some armhf programs.
 +
* -current is ARMv7-a, little endian, hardware float ("hard-float", "armhf"), EABI, therefore not compatible with most .pnd .
  
 
= Stable or -current ? =
 
= Stable or -current ? =
 
* Stable is for production use, ie. for work, as a server etc..
 
* Stable is for production use, ie. for work, as a server etc..
 
* -current is a work in progress. Although it's pretty usable, some things may be broken/unstable.
 
* -current is a work in progress. Although it's pretty usable, some things may be broken/unstable.
* I won't rebuild the 14.0 if there's no big bad bug, i'll just add important features as packages. Of course, official Slackware updates are included.
+
* -current rootfs may be smaller or bigger from build to build, as I can include or remove KDE, amongst other things.
* -current rootfs may be smaller or bigger from build to build, as i can include or remove KDE, amongst other things.
+
* If you want to help the development, I prefer that you use -current.
* If you want to help the development, i prefer that you use -current.
 
 
* And finally, -current repository may be empty. It's because a new stable release is out.
 
* And finally, -current repository may be empty. It's because a new stable release is out.
 +
 +
= A word about SOLEIL =
 +
* [http://pandorawiki.org/SOLEIL SOLEIL] is another project of mine, based on SL4P.
 +
* It's basically the same OS from the Pandora point of view, but has some neat extended features. Feel free to take a look at it.
 +
 +
= A word about security =
 +
* The shipped MPlayer is optimized, but outdated, if this is a concern, you can uninstall it and use the official Slackware up-to-date version instead.
 +
* Same applies for bluez, but note that there's no working up-to-date OP-compatible working package.
 +
* See also #Firefox, Thunderbird, SeaMonkey and Java-OpenJRE/JDK updates
 +
* SL4P's Bluetooth may be vulnerable to [https://mobile.slashdot.org/story/17/09/12/2030213/blueborne-vulnerabilities-impact-over-5-billion-bluetooth-enabled-devices this exploit].
  
 
= Media choice =
 
= Media choice =
 
* SL4P runs on a SD card. It fits well on 8G, but 16G or more are recommended if you plan to install all the pre-compiled packages.
 
* SL4P runs on a SD card. It fits well on 8G, but 16G or more are recommended if you plan to install all the pre-compiled packages.
 
* The SD card must support Linux filesystems, see [http://pandorawiki.org/SD_compatibility_list this SD compatibility chart].
 
* The SD card must support Linux filesystems, see [http://pandorawiki.org/SD_compatibility_list this SD compatibility chart].
* I myself recommend the [http://www.sandisk.com/products/memory-cards/sd/ SanDisk Extreme or Extreme Pro cards].
+
* I myself recommend the [http://www.sandisk.com/products/memory-cards/sd/ SanDisk Extreme, Extreme PLUS, or Extreme Pro cards].
  
 
= Installation =
 
= Installation =
 
Note: if you're a Linux noob, and you're scared by this Wiki page, check [http://boards.openpandora.org/index.php?/topic/11132-tutorial-format-your-sd-card-and-install-slackware-using-only-your-pandora/#entry206993 this simple tutorial] from F_Slim. Thanks to him.<br>
 
Note: if you're a Linux noob, and you're scared by this Wiki page, check [http://boards.openpandora.org/index.php?/topic/11132-tutorial-format-your-sd-card-and-install-slackware-using-only-your-pandora/#entry206993 this simple tutorial] from F_Slim. Thanks to him.<br>
 
Note: if you are one of the last windows users, you can install SL4P using the method nicely provided by ingoreis. Check [http://boards.openpandora.org/index.php?/topic/10548-slackware14rc3-for-pandora-pretty-easy-install-for-windows-users/ this thread.]
 
Note: if you are one of the last windows users, you can install SL4P using the method nicely provided by ingoreis. Check [http://boards.openpandora.org/index.php?/topic/10548-slackware14rc3-for-pandora-pretty-easy-install-for-windows-users/ this thread.]
* Format a 8G or more SD card with the Ext2 filesystem. To make explanations clear, name it SLACK.
+
* Format a 8G or more SD card with the Ext4 filesystem. To make explanations clear, name it SLACK.
 +
* You can disable the Ext4 journal to get a better performance, with the sdc1 partition for example:
 +
tune2fs -O ^has_journal /dev/sdc1
 +
* Note that Ext4 support is enabled since [http://openpandora.org/firmware/fullflash/ SuperZaxxon v1.75 firmware], so be sure to update. If you don't/can't, you can safely use Ext2 instead.
 
* If you don't know how to format a drive, use GParted under Linux, or run their [http://sourceforge.net/projects/gparted/files/latest/download?source=files Live-CD]. Here's the [http://gparted.sourceforge.net/display-doc.php?name=help-manual manual].
 
* If you don't know how to format a drive, use GParted under Linux, or run their [http://sourceforge.net/projects/gparted/files/latest/download?source=files Live-CD]. Here's the [http://gparted.sourceforge.net/display-doc.php?name=help-manual manual].
 
* It's highly recommended to have a second partition formated as a swap. 256M or more is a good choice. 512M is wiser is you plan to compile some stuff, or for server use.
 
* It's highly recommended to have a second partition formated as a swap. 256M or more is a good choice. 512M is wiser is you plan to compile some stuff, or for server use.
* If you don't plan to use this partition configuration (OS followed by swap), you'll have to edit the [http://www.tuxfiles.org/linuxhelp/fstab.html /media/SLACK/etc/fstab] after having uncompressed the rootfs.
+
* If you don't plan to use this partition configuration (OS followed by swap), you'll have to edit the [http://www.tuxfiles.org/linuxhelp/fstab.html /etc/fstab] after having uncompressed the rootfs.
 
* If you're cleaning up a previous SL4P installation for a fresh new one, proceed like this:
 
* If you're cleaning up a previous SL4P installation for a fresh new one, proceed like this:
 
  rm -rf /media/SLACK/*
 
  rm -rf /media/SLACK/*
Line 79: Line 129:
 
and sync:
 
and sync:
 
  sync
 
  sync
* Grab the latest 14.0 rootfs [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Frootfs here.]
+
* Grab the latest 14.2 rootfs [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.2%2Frootfs here.]
 
Or
 
Or
 
* Grab the latest -current (unstable) rootfs [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-current%2Frootfs here.] The -current repository may be empty. It's because a new stable release is out.
 
* Grab the latest -current (unstable) rootfs [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-current%2Frootfs here.] The -current repository may be empty. It's because a new stable release is out.
Line 97: Line 147:
  
 
= Autologin =
 
= Autologin =
* The Slim login manager, which is SL4P's default, can automatically log in an user. You're asked about it at the first login. Else, see /etc/slim.conf .
+
* The slim login manager, which is SL4P's default, can automatically log in an user. You're asked about it at the first login. Else, edit /etc/slim.conf to change the configuration.
 
* KDM works, but is too heavy. You have to edit /etc/rc.d/rc.4 in order to use it.
 
* KDM works, but is too heavy. You have to edit /etc/rc.d/rc.4 in order to use it.
  
 
= Basic usage =
 
= Basic usage =
* In order to type commands as root, you have to type su -. You can use just su, but i don't recommend it because you won't have the full root environment.
+
* In order to type commands as root, you have to type su -. You can use just su, but I don't recommend it because you won't have the full root environment.
* When using adduser, at some explicit point, push [up] to put this user in adequate groups.
 
 
* To choose a window manager, type xwmconfig.
 
* To choose a window manager, type xwmconfig.
* I ship those ones:
+
* I ship those:
 
  Xfce
 
  Xfce
 
  fluxbox
 
  fluxbox
Line 117: Line 166:
 
  wmii
 
  wmii
 
* In some -current or -RC builds, i ship KDE. Avoid selecting it as full desktop on 256M Pandora.
 
* In some -current or -RC builds, i ship KDE. Avoid selecting it as full desktop on 256M Pandora.
* To power off, or reboot your Pandora when not in Xfce and it's user-friendly menus, become root with:
+
* To power off, or reboot your Pandora when not in Xfce and its user-friendly menus, become root with:
 
  su -
 
  su -
 
and type:
 
and type:
Line 123: Line 172:
 
or  
 
or  
 
  reboot
 
  reboot
 +
 +
= Setting up your timezone =
 +
* Become root and use
 +
timeconfig
  
 
= Setting up your language =
 
= Setting up your language =
 
* You can set your locale pretty easily. First, you have to know which languages are available, type:
 
* You can set your locale pretty easily. First, you have to know which languages are available, type:
 
  locale -a
 
  locale -a
* Choose the one that suits best your need. I highly recommend to use the versions with .utf8 .
+
* Choose the one that best suits your need. I highly recommend to use the versions with .utf8 .
 
* Then be root and edit /etc/profile.d/lang.sh .
 
* Then be root and edit /etc/profile.d/lang.sh .
 
  su -
 
  su -
 
  emacs /etc/profile.d/lang.sh
 
  emacs /etc/profile.d/lang.sh
 
* You'll have to change this variable with the one you need:
 
* You'll have to change this variable with the one you need:
export LANG=<span style="color:#FF0000">en_US.UTF-8</span>
+
export LANG=<span style="color:#FF0000">en_US.UTF-8</span>
 +
* Save the file, make sure it's executable:
 
  chmod +x /etc/profile.d/lang.sh
 
  chmod +x /etc/profile.d/lang.sh
* Save the file and reboot.
+
* Reboot.
  
 
= Services started at boot =
 
= Services started at boot =
Line 149: Line 203:
 
= Installing a program from source =
 
= Installing a program from source =
 
* The cleanest way to do it is to use a SlackBuild script: http://slackbuilds.org/guidelines/
 
* The cleanest way to do it is to use a SlackBuild script: http://slackbuilds.org/guidelines/
* Many SlackBuilds for Slackware 14.0 are already available here: http://slackbuilds.org/repository/14.0/
+
* Many SlackBuilds for Slackware 14.2 are already available here: http://slackbuilds.org/repository/14.2/
 
* I shipped a tool named sbopkg, which does the job for you. Become root using su - , then sync it with the internet repository with:
 
* I shipped a tool named sbopkg, which does the job for you. Become root using su - , then sync it with the internet repository with:
 
  sbopkg -r
 
  sbopkg -r
* The sync will take a long time. Once you've done that, run
+
* The sync may take some time. Once you've done that, run
 
  sh /root/sboflags.sh
 
  sh /root/sboflags.sh
to optimize the builds for the Pandora.
+
to optimize the builds for the Pandora. You have to run this script after every sync.
* You have to run this script after every sync. A fistful of programs (like ilbc or lua, which need -fPIC) will still need a bit of tweaking.
 
 
* Then all is set up, you just have to use
 
* Then all is set up, you just have to use
 
  sbopkg
 
  sbopkg
Line 166: Line 219:
 
  ls /var/log/packages/libgnomecanvas*
 
  ls /var/log/packages/libgnomecanvas*
 
* Also note that gnome libraries must be compiled in a certain order. I already did the job, and shipped them in the rootfs.
 
* Also note that gnome libraries must be compiled in a certain order. I already did the job, and shipped them in the rootfs.
* If you don't use a SlackBuild script, then the procedure almost always ends like:
+
* If you don't use a SlackBuild script, then the Slackware procedure almost always ends like:
 
  make install DESTDIR=/tmp/whatever/
 
  make install DESTDIR=/tmp/whatever/
 
  cd /tmp/whatever/
 
  cd /tmp/whatever/
 
  makepkg /tmp/whatever-1.0.0-arm-1.tgz
 
  makepkg /tmp/whatever-1.0.0-arm-1.tgz
 
  installpkg /tmp/whatever-1.0.0-arm-1.tgz
 
  installpkg /tmp/whatever-1.0.0-arm-1.tgz
 +
* If checking and fixing all of those pesky dependencies manually is too much of a burden for you to bear: fear not! [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Sqg Sqg] (slackbuilds queue generator) saves your day!
  
 
= Installing a program with a precompiled archive =
 
= Installing a program with a precompiled archive =
* I compiled a lot (300+) of packages from http://slackbuilds.org/.
+
* I compiled a lot (450+) of packages from http://slackbuilds.org/.
 
* I shipped a graphical install tool named GSlapt. Launch it with its icon, update the package list, then install what you need, checking the dependencies of your programs here:  http://slackbuilds.org/
 
* I shipped a graphical install tool named GSlapt. Launch it with its icon, update the package list, then install what you need, checking the dependencies of your programs here:  http://slackbuilds.org/
* You can also proceed manually. Find 14.0 packages [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Fpackages%2Fextra here], and -current ones [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-current%2Fpackages%2Fextra here.]
+
* You can also proceed manually. Find 14.2 packages [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.2%2Fpackages%2Fextra here], and -current ones [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-current%2Fpackages%2Fextra here.]
 
* Download what you need, checking the dependencies of your programs here:  http://slackbuilds.org/
 
* Download what you need, checking the dependencies of your programs here:  http://slackbuilds.org/
 
* Put all needed .tgz or .txz in a folder, go root using su -, then type:
 
* Put all needed .tgz or .txz in a folder, go root using su -, then type:
Line 183: Line 237:
 
= About SL4P precompiled archives =
 
= About SL4P precompiled archives =
 
* All shipped and extra archives are compiled with sbopkg with Pandora-optimized flags.
 
* All shipped and extra archives are compiled with sbopkg with Pandora-optimized flags.
  -DPANDORA -O2 -pipe -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp
+
  -DPANDORA -O2 -pipe -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fPIC
 
* The links to the sources are located here: http://slackbuilds.org/repository/
 
* The links to the sources are located here: http://slackbuilds.org/repository/
 
* The building order is fixed in queue files, kind of build playlist.
 
* The building order is fixed in queue files, kind of build playlist.
 
* The queues are located in /var/lib/sbopkg/queues/
 
* The queues are located in /var/lib/sbopkg/queues/
* About [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Fpackages%2Fshipped shipped] archives, you don't need to download them as they're already in the rootfs, see [http://pandorawiki.org/Software_projects/OS/Slackware/Build-system this.]
+
* About [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.2%2Fpackages shipped] archives (base and base-more), you don't need to download them as they're already in the rootfs, see [http://pandorawiki.org/Software_projects/OS/Slackware/Build-system this.]
* Some archives won't work, like Kompozer, because it's a repackaging of x86 binaries. As i'm not yet in the process of fine-tuning, i left them for now.
+
* Some archives won't work, like Kompozer, because it's a repackaging of x86 binaries. As I'm not yet in the process of fine-tuning, I left them for now.
  
 
= Installing KDE 4 =
 
= Installing KDE 4 =
Line 194: Line 248:
 
  slackpkg update
 
  slackpkg update
 
  slackpkg install kde
 
  slackpkg install kde
* Note that although i already slimmed down KDE configuration files for less eye-candy, the 512M Pandora is recommended to run the full desktop.
+
* Note that although i already slimmed down KDE configuration files for less eye-candy, a 512M Pandora is recommended to run the full desktop.
* Anyway, you can run any KDE application (konqueror, kwrite...) flawlessly with the 256M version.
+
* Anyway, you can run any KDE application (konqueror, kwrite...) flawlessly with the 256M version running Xfce.
* Type xwmconfig to select KDE.
+
* Type xwmconfig to select KDE, or any other window manager.
  
 
= Updates =
 
= Updates =
* You may eventually read [ftp://ftp.armedslack.org/slackwarearm/slackwarearm-14.0/ChangeLog.txt the Slackware ARM 14.0 changelog here]
+
* You may eventually read [ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.2/ChangeLog.txt the Slackware ARM 14.2 changelog here]
 
* If you need an up-to-date security, you should consider subscribing to the main [http://slackware.com/lists/ Slackware mailing list]. Slackware ARM updates are generally available a bit later.
 
* If you need an up-to-date security, you should consider subscribing to the main [http://slackware.com/lists/ Slackware mailing list]. Slackware ARM updates are generally available a bit later.
 
* For stable releases, plug the net, become root using su -, then type:
 
* For stable releases, plug the net, become root using su -, then type:
 
  slackpkg update
 
  slackpkg update
 
  slackpkg upgrade-all
 
  slackpkg upgrade-all
* Do not use slackpkg when using a -current. Instead, look at the [ftp://ftp.armedslack.org/slackwarearm/slackwarearm-current/ChangeLog.txt changelog], download packages from [ftp://ftp.armedslack.org/slackwarearm/slackwarearm-current/slackware/ here], become root using su -, then type:  
+
* Do not use slackpkg when using a -current. Instead, look at the [ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/ChangeLog.txt changelog], download packages from [ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/slackware/ here], become root using su -, then type:  
 
  upgradepkg /path/to/the/updates/*.t?z
 
  upgradepkg /path/to/the/updates/*.t?z
 
Note that some packages like a/aaa_elflibs are not supposed to be upgraded in -current. A new rootfs is needed.
 
Note that some packages like a/aaa_elflibs are not supposed to be upgraded in -current. A new rootfs is needed.
  
* You can also set up a cronjob. In this case, check /etc/slackpkg/blacklist to ensure some critical packages (ie., kernel) will not be updated.
+
* You can eventually set up a cronjob. In this case, check /etc/slackpkg/blacklist to ensure some critical packages (e.g. kernel) will not be updated.
 
* Slackware usually provides updates during 10+ years, but it seems to be less with Slackware ARM. See [http://www.armedslack.org/ the news for more details].
 
* Slackware usually provides updates during 10+ years, but it seems to be less with Slackware ARM. See [http://www.armedslack.org/ the news for more details].
  
 
= SL4P-specific updates =
 
= SL4P-specific updates =
 
* I provide Pandora fixes, available as Slackware archives.
 
* I provide Pandora fixes, available as Slackware archives.
* 14.0 fixes are located [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Fpackages%2Fupdates here.]
+
* Simply use GSlapt, and update.
* Grab them, become root using su -, then type:
 
upgradepkg --install-new /path/to/the/updates/*.t?z
 
* You don't need to install those updates when using a rootfs build more recent than the update.
 
  
 
= Firefox, Thunderbird, SeaMonkey and Java-OpenJRE/JDK updates =
 
= Firefox, Thunderbird, SeaMonkey and Java-OpenJRE/JDK updates =
* Slackware ARM 14.0 doesn't provide anymore updates for Firefox, Thunderbird and SeaMonkey because of a build problem.
+
* Slackware ARM 14.2 doesn't provide anymore updates for Firefox, Thunderbird and SeaMonkey because of a build problem.
 
* You have to download the unsupported -current archives and update them manually, using the method mentioned above.
 
* You have to download the unsupported -current archives and update them manually, using the method mentioned above.
* Get them [ftp://ftp.armedslack.org/slackwarearm/unsupported/slackwarearm-current/packages/ here].
+
* Get them [ftp://ftp.arm.slackware.com/slackwarearm/unsupported/slackwarearm-current/packages/ here].
 
* About Java-OpenJRE/JDK, it's not possible to update them through slackpkg because it was added on-the-fly to Slackware ARM.
 
* About Java-OpenJRE/JDK, it's not possible to update them through slackpkg because it was added on-the-fly to Slackware ARM.
* Check and get the updates [ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.0/patches/packages/ here].
+
* Check and get the updates [ftp://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.2/patches/packages/ here].
 
* Be sure to download and update both as the jre is not included in the jdk.
 
* Be sure to download and update both as the jre is not included in the jdk.
  
 
= Kernel updates =
 
= Kernel updates =
* I provide kernel updates, and also a real time kernel.
+
* I provide kernel updates through GSlapt.
* You don't need to install those updates when using a rootfs build more recent than the update.
+
* Many kernels are already available in the rootfs, like real time, or non-debug.
* To know which kernel currently runs, type:
+
* To know which kernel is currently running, type:
 
  uname -r
 
  uname -r
* Grab the latest kernel pack from [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Fpackages%2Fkernels here.]
 
* Install it with:
 
su -
 
upgradepkg --install-new kernels-[yyyymmdd]-arm-1.tgz
 
 
* To enable a new kernel, for example 3.2.30-szfinal or the 3.2.26-rt, do:
 
* To enable a new kernel, for example 3.2.30-szfinal or the 3.2.26-rt, do:
 
  cd /boot
 
  cd /boot
Line 243: Line 290:
 
  rm uImage
 
  rm uImage
 
  cp uImage-3.2.26-rt uImage
 
  cp uImage-3.2.26-rt uImage
* Then link the right modules for the right kernel.
 
cd /lib/modules
 
* Get the current kernel name:
 
uname -r
 
* Remove the current kernel modules link, for example 3.2.30:
 
rm -rf 3.2.30
 
* Now link to the new modules. If the target kernel name contains "dirty", i.e. 3.2.30-dirty-displaylink, keep it in the modules folder name:
 
ln -s 3.2.30-dirty-displaylink 3.2.30-dirty
 
 
And reboot.
 
And reboot.
 
* If lsmod reports that no modules are loaded (that means, eg., no touchscreen), then run as root:
 
* If lsmod reports that no modules are loaded (that means, eg., no touchscreen), then run as root:
 
  depmod -a
 
  depmod -a
 
 
And reboot again.
 
And reboot again.
  
 
= Automounting a SD card or an USB drive =
 
= Automounting a SD card or an USB drive =
* No system-wide automounter is enabled for now. It's still a work in progress and not perfect so i don't include this for now.
+
* No system-wide automounter is enabled for now.
* Only Xfce automounts.
+
* Only Xfce and some other window managers do automount.
 
* As Xfce mounts devices at insertion, if you booted with a second SD card or an USB drive plugged in, you have to click on the device icon.
 
* As Xfce mounts devices at insertion, if you booted with a second SD card or an USB drive plugged in, you have to click on the device icon.
 
* If you plan to use Minimenu, you currently have to automount under Xfce, run xwmconfig, then log out to run Minimenu. This is the best method to save RAM.
 
* If you plan to use Minimenu, you currently have to automount under Xfce, run xwmconfig, then log out to run Minimenu. This is the best method to save RAM.
Line 271: Line 309:
 
Near the top, change
 
Near the top, change
 
  #modprobe ehci-hcd
 
  #modprobe ehci-hcd
#modprobe g_cdc
 
 
into:
 
into:
 
  modprobe ehci-hcd
 
  modprobe ehci-hcd
modprobe g_cdc
 
  
 
= Fixing the endless reboot =
 
= Fixing the endless reboot =
Line 280: Line 316:
 
* Boot SL4P, when prompted to enter the root password for maintenance, do it, then type:
 
* Boot SL4P, when prompted to enter the root password for maintenance, do it, then type:
 
  fsck -y /dev/mmcblk0p1
 
  fsck -y /dev/mmcblk0p1
 +
* You can do the same under Zaxxon. Note that it will be /dev/mmcblk1p1 if SL4P is on a second card.
 +
* You will be warned if the card is still mounted, so unmount it, and proceed.
  
 
= Changing the Hostname =
 
= Changing the Hostname =
 
* See [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Hostname this.]  
 
* See [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Hostname this.]  
 +
 +
= Switching from 1GHz to 600MHz Pandora =
 +
* I slightly modified the clock script to split the parameters into two categories: 1Ghz and 600MHz.
 +
* You can safely put SL4P in any OP, and have a max OPP + max MHz settings for each as the model is recognized at boot, then clocked.
 +
* It's totally transparent, just set your parameters as usual.
  
 
= Fast boot tweak =
 
= Fast boot tweak =
 
* I moved some of the boot stuff (ldconfig, font cache, mime database) in /etc/rc.d/rc.local_shutdown.
 
* I moved some of the boot stuff (ldconfig, font cache, mime database) in /etc/rc.d/rc.local_shutdown.
 
* The reboot/power off process is slowered, but the OS integrity is safe.
 
* The reboot/power off process is slowered, but the OS integrity is safe.
 +
 +
= Bluetooth audio =
 +
* SL4P already has everything you need. '''Don't''' even start with pulseaudio (unless you really need to)!
 +
 +
==== Proper Bluetooth configuration ====
 +
* We need to enable access to the BT protocols we want to use:
 +
* Fix '''/etc/bluetooth/audio.conf''' with:
 +
<syntaxhighlight lang="bash">
 +
[General]
 +
Enable=Source,Sink,Headset,Socket,Control
 +
</syntaxhighlight>
 +
 +
==== Find your BT device's MAC address ====
 +
* Enable Bluetooth on your pandora.
 +
* If the BT device manager doesn't pop up automatically, start it with:
 +
<syntaxhighlight lang="bash">
 +
blueman-manager
 +
</syntaxhighlight>
 +
* Make sure your device can be found (i.e. is not paired with another computer or mobile phone etc.)!
 +
* Search for your device and find it's MAC address.
 +
* '''Don't''' connect to/pair with your device yet!
 +
 +
==== Proper ALSA configuration ====
 +
* We will define a new bluetooth device and route '''all''' ALSA traffic through it.
 +
* This means your BT device will be the default ALSA output device!
 +
* Fix '''~/.asoundrc''' with your MAC address:
 +
<syntaxhighlight lang="bash">
 +
pcm.btheadset {
 +
type plug
 +
slave {
 +
pcm {
 +
type bluetooth
 +
device "[ADD MAC HERE]"
 +
profile "auto"
 +
}
 +
}
 +
 +
hint {
 +
show on
 +
description "BT Headset"
 +
}
 +
}
 +
 +
ctl.btheadset {
 +
type bluetooth
 +
}
 +
</syntaxhighlight>
 +
* Fix '''/etc/asound.conf''' with your MAC address:
 +
<syntaxhighlight lang="bash">
 +
pcm.!default {
 +
type bluetooth
 +
device "[ADD MAC HERE]"
 +
}
 +
</syntaxhighlight>
 +
* Reboot and pair with your device using the '''A2DP''' protocol.
 +
* Enjoy BT audio with your Slackware and your Pandora :)
 +
 +
= SGX drivers installer =
 +
* With notaz's blessing, i tweaked his SGX drivers installer to make it work both under SL4P and Zaxxon.
 +
* Get it [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Ftools%2Fsgx_drivers_installer here.]
 +
* You can safely remove your old version.
  
 
= PND compatibility list =
 
= PND compatibility list =
 
* SL4P supports .pnd files.
 
* SL4P supports .pnd files.
* PNDs used to be recognized automatically. It's not the case anymore, and i don't know why.
+
* PNDs used to be recognized automatically. It's not the case anymore, and I don't know why.
* So here's the workaround: after the insertion of your SD or USB drive, you have to push the [http://boards.openpandora.org/index.php?app=core&module=attach&section=attach&attach_rel_module=post&attach_id=4449 green button] near the Xfce menu.
+
* So here's the workaround: after the insertion of your SD or USB drive, you have to push the green button near the Xfce menu.
 
* Due to 3.2 kernel and dynamically linked libraries, not all .pnd are compatible.
 
* Due to 3.2 kernel and dynamically linked libraries, not all .pnd are compatible.
 +
* If a pnd doesn't work, first thing to check is its log file in /tmp .
 
* [[Software_projects/OS/Slackware/PND-compatibility-list|View the PND compatibility list here.]]
 
* [[Software_projects/OS/Slackware/PND-compatibility-list|View the PND compatibility list here.]]
  
Line 299: Line 404:
 
* All those guides are applicable to any version of Slackware, ie. x86, x86_64, IBM mainframe, etc.  
 
* All those guides are applicable to any version of Slackware, ie. x86, x86_64, IBM mainframe, etc.  
 
* Follow this [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage link.]
 
* Follow this [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage link.]
 
= Xfce layout chooser =
 
* This is a beta work and may or may not be included in a release.
 
* The icon is located in "System".
 
* I'm developing it, it's currently in beta stage.
 
* You can save your own Xfce configuration, and load others.
 
* If you want to use it, please use the save feature prior to anything else.
 
* Only one custom layout is available right now.
 
  
 
= Sources =
 
= Sources =
Line 314: Line 411:
 
= Build system =
 
= Build system =
 
* I distribute it under the GPL 3 license.
 
* I distribute it under the GPL 3 license.
* It may look a bit messy for now (and indeed, some part have to be cleaned), but it's versatile, as i intended from the start.
+
* It may look a bit messy for now (and indeed, some part have to be cleaned), but it's versatile, as I intended from the start.
 
* It's mainly three bash scripts.
 
* It's mainly three bash scripts.
 
* You need a Pandora to run the third one.
 
* You need a Pandora to run the third one.
Line 325: Line 422:
  
 
= Ask a question/Report a bug =
 
= Ask a question/Report a bug =
* You're welcome, and please post [http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/ here] or [http://boards.openpandora.org/index.php?/topic/9797-slackware-for-pandora-140/ here.]
+
* You're welcome to do so, and please post [http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/ here] or [http://boards.openpandora.org/index.php?/topic/9797-slackware-for-pandora-140/ here.]
 
 
Software projects/OS/Slackware/Advanced usage
 
 
 
= Development =
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Distributed_compilation Distributed compilation between two or more Pandoras.]
 
 
 
= Multimedia =
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/CUPS Common Unix Printing System.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Image_scanning Image scanning.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Non-Free_codecs Installing non-Free codecs.]
 
 
 
= Network - Readme =
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Network_get_started Get Started.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Hostname Changing the hostname/domain name.]
 
 
 
= Network =
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Apache Apache web server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/DHCP_server DHCP server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Firewall Firewall/Gateway/NAT router/QoS.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/ProFTPD FTP server ProFTPD.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/vsftpd FTP server vsftpd.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Inetd Inetd super-server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Bonding Network interfaces link aggregation.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/NFS NFS server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/PXE_boot_server PXE boot server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Samba Samba server.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/SSH SSH.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/VNC VNC.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/VPN VPN.]
 
 
 
= Security =
 
* Antivirus for non-*NIX machines.
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/System_encryption System encryption.]
 
* Slackware hardening.
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Rootkit_scanners Rootkit scanners.]
 
 
 
= System =
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Kernel Kernel compiling.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Partitioning_and_formatting Partitioning/formatting.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/RAID RAID setup.]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/USB_graphic USB external graphic cards (DisplayLink, SiS USB2VGA).]
 
* [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Virtual_machines Virtual machines.]
 
 
 
= Links =
 
* [http://docs.slackware.com/ The Slackware Documentation Project.]
 
* [http://www.linuxquestions.org/linux/answers LinuxQuestions.org's tutorials.]
 
* [http://www.linuxquestions.org/questions LinuxQuestions.org's forums.]
 
* [http://www.armedslack.org/mailinglist/ Slackware ARM mailing list.]
 
 
 
Software projects/OS/Slackware/Build-system
 
 
 
= Principles =
 
* It's not a one run and go. You need time and patience if you want a full and complete release. Anyway, you can get a minimal alpha build relatively fast.
 
* The target directory is likely to be a SD card. 8G is recommended as a minimum.
 
* Phase 1 populates the target directory with the main ARMedslack Linux distribution and some crucial stuff like the Pandora kernel.
 
* Phase 2 populates the target directory with parts from official Open Pandora OS and tweaked stuff.
 
* A specific part of rc.local is executed during the first boot on a Pandora.
 
* The files folder contains tweaked stuff.
 
* The pkg folder contains pre-built packages from previous alpha builds.
 
* The sources folder contains sources for essential programs.
 
* Some proprietary stuff is missing, like 3D drivers. They are useful only if you want to compile your own kernel. Check the Open Pandora git repository for them.
 
 
 
= Get the build system =
 
* Get the archive [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-14.0%2Fbuild-system here.]
 
* If you don't run a Slackware or a derivative, get the Slackware's installpkg script [http://slackware.openpandora.org/pandora/index.php?dir=sl4p%2Fsl4p-13.37%2Fbuild-system here.] Put it in /sbin and make it executable.
 
 
 
= Dependencies =
 
* You need to download the official Open Pandora rootfs: http://openpandora.org/firmware/pandora-rootfs.tar.bz2
 
* Uncompress it as root anywhere and link it to the build directory as "pandora-rootfs".
 
* Format a 8G or more SD card with the Ext2 filesystem. To make explanations clear, name it SLACK.
 
* If you don't know how to format a drive, use GParted under Linux, or run their [http://sourceforge.net/projects/gparted/files/latest/download?source=files Live-CD]. Here's the [http://gparted.sourceforge.net/display-doc.php?name=help-manual manual.]
 
* It's highly recommended to have a second partition formated as a swap. 256M or more is a good choice.
 
 
 
= Bash knowledge =
 
* You need minimal bash knowledge in order to understand and succeed. [http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29 This] is a good start.
 
* Each script contains comments. Read them.
 
 
 
= rc.local =
 
* rc.local will be copied and executed automatically on the Pandora. You have to tweak it before Phase 1 or Phase 2.
 
* Remove simple-comments in order to produce the needed packages during the first boot.
 
* Put the SD card in the Pandora, and power it on.
 
* The Pandora will build many needed packages, but not all listed, because of some dependencies installed later through sbopkg.
 
* You have to edit the OPP="" and MHZ="" variables at the top of the script for your Pandora unit(s). These will only be used during the build phases.
 
 
 
= Phase 1 =
 
* Run as su -.
 
* You'll see packages errors because it's a first run.
 
 
 
= Phase 2 =
 
* Run as su -.
 
* Now, you can unmount the card and boot normally this alpha build on the Pandora.
 
 
 
= After that first boot =
 
* The Pandora will power off after having done the job. May last for one hour or two.
 
* Remove the card.
 
* Save all /media/SLACK/tmp/*.t?z in the local repository listed in the PHASE-2.sh
 
MYPKGS="$CWD/pkg"
 
folder of the build system.
 
 
 
= In-between steps =
 
* Plug the net.
 
* Launch sbopkg as su -, load the vrac1 queue file, process it saying yes (Q) to options and wait. This is gonna be very long. I really mean very.
 
* Do the same with vrac2 and vrac3.
 
* Save all /tmp/*.t?z in the
 
MYPKGSMORE="$CWD/pkg-more"
 
folder of the build system.
 
* Be careful with disk space, you may fill the card. If so, save and erase all /tmp/*.t?z, and sources inside /var/cache/sbopkg/ between queues processing.
 
* Note that i include other packages listed in other queue files in my own release. If you plan to do so, move them in MYPKGSMORE="$CWD/pkg-more".
 
 
 
= Final step =
 
* Populate a new SD card, with PHASE-1.sh and PHASE-2.sh
 
* Edit /media/SLACK/etc/rc.d/rc.local to build the remaining packages to put in MYPKGS="$CWD/pkg"
 
* Put the SD card in the Pandora, and power it on.
 
* The Pandora will generate final needed packages.
 
* The Pandora will power off after having done the job. May last for one hour or two.
 
* Remove the card.
 
* Save all /media/SLACK/tmp/*.t?z in YPKGS="$CWD/pkg" folder of the build system.
 
* Now, you can create a complete SL4P system.
 
 
 
= Creating a compressed rootfs =
 
* Populate a SD card. Now you should know how to do it ;^).
 
* Boot it on a Pandora.
 
* Once the Pandora shuts down, remove the card, and follow [http://pandorawiki.org/How_to_back_up_a_Root_File_System_%28on_an_SD_Card%29_to_an_SD_Card this] procedure.
 
 
 
= Special packages =
 
* In the sources folder, you'll find some programs that aren't automatically generated by the build system.
 
I don't list those dependencies for now, because i do more useful things ^^.
 
* XMMS may just needs libmikmod.
 
* Qt3 is a bit long to build. It should be built before the big playlist.
 
 
 
= Sources =
 
* Apart what i already mentioned here, some SL4P part are taken directly from the official Open Pandora OS.
 
* Sources are directly related to the build date, ie. if i upload a release the 1st april 2012, so the sources are related to the corresponding Open Pandora OS, rootfs, pandora-firmware, pandora-libraries, etc.
 
* Same thing for binaries coming from the official OP rootfs.
 
* About pre-compiled packages, shipped or not, grab the sources + SlackBuild accordingly to the version [http://slackbuilds.org/ here].
 
* If some package version changed, you have access to the old data using [http://slackbuilds.org/cgit/slackbuilds/ sbopkg git repo].
 
 
 
= Notes =
 
* It may look a bit messy for now (and indeed, some part have to be cleaned), but it's versatile, as i intended from the start.
 
* Depending on what you comment/uncomment, you can produce an alpha build, very minimal, or a full build.
 
* Depending on what you edit, you can use it to port any *NIX to Open Pandora, and maintain your build very easily
 
* The -current build system is under work and is not released yet.
 
 
 
= Ask a question/Report a bug =
 
* You're welcome, and please post here: http://boards.openpandora.org/index.php?/topic/1524-slackware-inside-pandora/
 
 
 
projects/OS/Slackware/Advanced usage/Network get started
 
 
 
= Network interfaces =
 
* eth0 is the interface that shows up when you plug an USB to ethernet adapter. A list of compatible ones is located [http://pandorawiki.org/USB_compatibility_list#USB_to_Ethernet_adapters here].
 
* wlan0 is the embedded Wi-fi interface.
 
* wlan1 (or wlan2, wlan3 etc.) is the name of a Wi-fi dongle.
 
* usb0 should be the small USB port (not sure, may be the first plugged).
 
* usb1 should be the big USB port (not sure).
 
Anyway, you can check the physical link connectivity, as root:
 
ethtool usb0
 
ethtool usb1
 
ethtool eth0
 
* If you connect an OP with another using an USB cable, the OP at the little end of the cable will dramatically drain the current from the other OP's big USB port.
 
* To avoid this, at the little end, type as root:
 
echo 0 > /sys/class/power_supply/twl4030_usb/enable
 
* With this usb-usb connection, you have to:
 
rmmod g-cdc
 
* To permanently remove this module, edit /etc/rc.d/c.local and change
 
modprobe g_cdc
 
into
 
#modprobe g_cdc
 
* There's also a bluetooth interface, but until now i just connected a mouse, so can't tell much about it.
 
* These interface numbers (eth0, eth1 etc.) may vary, depending which one you plug first.
 
* The numbers can be fixed using the /etc/udev/rules.d/70-persistent-net.rules file.
 
* This file is deleted at each shutdown. To make use of it, edit /etc/rc.d/rc.local_shutdown , and comment this line:
 
rm /etc/udev/rules.d/70-persistent-net.rules
 
into
 
#rm /etc/udev/rules.d/70-persistent-net.rules
 
 
 
= SL4P default setup =
 
* The Network Manager, well, manages the connections, and asks for an IP address through a DHCP request. This is how it acts when you boot SL4P for the first time.
 
* You can set it up through a right-click on the NM-applet Xfce desktop icon (two little screens at bottom-right).
 
* Although it's shipped in the Slackware ARM release, i grabbed and compiled a more recent version.
 
 
 
= Slackware alternative setup =
 
* Wicd is included in the stock Slackware ARM extra packages.
 
* I don't include it anymore inside 14.0 but you still can install it, using slackpkg or any other method.
 
* I tried it only a bit so i can't recommend it, or not.
 
* If you want to give it a try, be root, then install it, and disable the network manager:
 
chmod -x /etc/rc.d/rc.networkmanager
 
* Activate Wicd at boot:
 
chmod +x /etc/rc.d/rc.wicd
 
* Activate Wicd frontend under Xfce. Go in the menu -> Settings -> Session and Startup -> Application Autostart tab, then check "Wicd Network Manager Tray".
 
* Reboot.
 
 
 
= Slackware default setup =
 
* Historically speaking, stock Slackware doesn't use the Network Manager, nor Wicd. The network is established at boot, once for all.
 
* If you want a non-graphical server-oriented setup, you have to disable the network manager (or Wicd).
 
chmod -x /etc/rc.d/rc.networkmanager
 
or
 
chmod -x /etc/rc.d/rc.wicd
 
* Run as root:
 
netconfig
 
* The hostname MUST BE:
 
darkstar
 
otherwise you'll break some Pandora scripts compatibility. Sudo won't launch anything with the wrong hostname.
 
* Set you parameters.
 
* Eventually edit /etc/rc.d/rc.inet1.conf to finalize your setup.
 
* Be sure to have all used interfaces plugged in when booting. With the deactivation of the network manager, it's no more plug and play.
 
* Reboot.
 
 
 
= Older Wiki page =
 
* 13.37 page is located [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Network_get_started-13.37 here].
 
 
 
Software projects/OS/Slackware/Advanced usage/Kernel
 
 
 
= Kernel: to recompile or not to recompile ? =
 
* You don't have to if you don't need to add a new feature.
 
* You don't have to if there's no urgent security kernel update.
 
* If you want to acquire a lot of global Linux knowledge, or if you are just curious, then yes, just go for it.
 
 
 
= Is it simple or complicated to recompile ? =
 
* Both.
 
* But as there's a default kernel configuration file for Open Pandora, it's pretty easy.
 
 
 
= Downloading and pre-configuring the latest kernel sources =
 
== Directly on the Pandora ==
 
* I wrote a script to automatize the OP kernel sources download and preparation.
 
* Plug the net, be root, then:
 
sh /root/kernel-sync.sh
 
* It's very long because of the 16MB/s SD slots throughput.
 
 
 
== From a PC ==
 
If you prefer to speed up the process and download them from your computer, then proceed like this (assuming your SD card is mounted under /media/SLACK/):
 
mkdir -p /media/SLACK/usr/src/
 
cd /media/SLACK/usr/src/
 
 
git clone git://openpandora.org/pandora-kernel.git
 
 
ln -s pandora-kernel linux
 
 
cd pandora-kernel
 
 
git checkout --track -b pandora-3.2 origin/pandora-3.2
 
* Then boot the pandora, and do this as root:
 
cd /usr/src/linux
 
make omap3_pandora_defconfig
 
 
 
= The fun part: tweaking =
 
* The configuration is stored in a hidden file named /usr/src/linux/.config
 
* You can use many tools to edit the configuration.
 
* The kamikaze way: edit manually the .config . Don't do that.
 
* The lazy way: install KDE and use as a user:
 
gksu make xconfig
 
* The common way, which i recommend:
 
make menuconfig
 
== Menuconfig ==
 
* Kernel options are stored in a tree.
 
* Options can be marked as [*] built-in, or <M> module.
 
* The vast majority of those options refers to a driver or a functionality.
 
* Built-in means inside the kernel, so once the kernel boots, you can't remove or change parameters.
 
* Module means you can either add or remove them after the boot. Ever typed "modprobe ehci-hcd" ?
 
* The example below is copied from my PC, will copy a real OP one later.
 
Arrow keys navigate the menu.  <Enter> selects submenus --->.  Highlighted letters are hotkeys.  Pressing <Y> includes, <N>
 
excludes, <M> modularizes features.  Press <Esc><Esc> to exit, <?> for Help, </> for Search.  Legend: [*] built-in  [ ]
 
excluded  <M> module  < > module capable
 
[*] DMA memory allocation support
 
General setup  --->
 
[*] Enable loadable module support  --->
 
[*] Enable the block layer  --->
 
Processor type and features  --->
 
Power management and ACPI options  --->
 
Bus options (PCI etc.)  --->
 
Executable file formats / Emulations  --->
 
[*] Networking support  --->
 
Device Drivers  --->
 
Firmware Drivers  --->
 
File systems  --->
 
hacking  --->
 
options  --->
 
Cryptographic API  --->
 
Virtualization  --->
 
Library routines  --->
 
<Select>    < Exit >    < Help >
 
 
 
== A simple tweak ==
 
* Highlight  Cryptographic API  --->
 
* Push [enter]. You're now in the Cryptographic API section.
 
* With [space], select all cryptographic algorithms you can. Ensure they are marked as <M>, not <*>.
 
* With [right], select < Exit >, then push [enter].
 
* Again, with [right], select < Exit >, then push [enter].
 
* Now push [enter], saying <Yes> to "Do you wish to save your new configuration ?".
 
* You're now ready to compile a kernel which will drive James Bond angrily jealous.
 
 
 
= Kernel compilation =
 
* Be sure you've overclocked your OP to the maximum MHz.
 
* At 800MHz, it's a 3+ hours job.
 
* Now you can compile it with another custom script:
 
sh /root/kernel.sh
 
* Reboot.
 
 
 
= Speed up the compilation time using two or more Pandoras =
 
* Read [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Distributed_compilation this], and set up your Pandoras.
 
* Make the adequate changes in /root/kernel-dist.sh with your editor of choice.
 
* Then compile with:
 
sh /root/kernel-dist.sh
 
* Reboot.
 
 
 
= 3D driver =
 
* So you booted your OP with your brand new kernel, but you can't run 3D apps. Again, two custom scripts for lazy people.
 
* Download the sources:
 
sh /root/3d-get-sources.sh
 
* Compile and install them:
 
sh /root/3d-compile.sh
 
* Reboot.
 
  
= Older Wiki page =
 
* 13.37 page is located [http://pandorawiki.org/Software_projects/OS/Slackware/Advanced_usage/Kernel-13.37 here].
 
  
  
 
[[Category:Development]]
 
[[Category:Development]]
[[Category:Kernel]]
 
[[Category:Network]]
 
[[Category:Security]]
 
 
[[Category:Software]]
 
[[Category:Software]]
 
[[Category:Slackware]]
 
[[Category:Slackware]]
 
[[Category:System]]
 
[[Category:System]]

Latest revision as of 17:48, 16 April 2021

Slackware logo

Disclaimer

Hi, this is Linux-SWAT.

Welcome to the SL4P, Slackware for Pandora, Wiki pages.

SL4P is a Slackware ARM overlay. Slackware ARM is the official ARM Slackware port.
Slackware ARM was formerly known as ARMedslack.

The 14.2 release forum page is located here: https://pyra-handheld.com/boards/threads/slackware-for-pandora-14-2.80934/

The technical and -current forum page is located here: https://pyra-handheld.com/boards/threads/slackware-inside-pandora.60258/

I'm the maintainer of this Slackware port, and you can find me here: https://pyra-handheld.com/boards/members/linux-swat.18403/

If you have questions, I suggest you to share it on the boards, not asking me privately.

Important notes: SL4P is not affiliated in any way with Slackware or Slackware ARM.
Please DO NOT contact any of them if you have problems with it. Contact ME.

SL4P is not affiliated in any way with Open Pandora GmbH or Open Pandora Ltd.
Please DO NOT contact any of them if you have problems with it. Contact ME.

This software is distributed as is. You are on your own responsibility when using it.

I distribute this documentation under the GPL 3 license. http://www.gnu.org/licenses/gpl.html

Features

  • Full hardware support
  • 12 window managers, including Xfce, Minimenu and Enlightenment DR17
  • KDE (512M RAM recommended), installed via internet in two commands
  • Pnd support
  • PNDmanager and PNDstore support
  • Armhf compatibility layer
  • Rebuilt optimized video player (MPlayer2)
  • Integrated YouTube player (SMTube, no Flash plugin needed)
  • Rebuilt optimized audio player (XMMS)
  • Integrated VOIP with Linphone
  • Integrated office suite, with AbiWord and Gnumeric
  • Integrated DisplayLink support
  • More than 400 Pandora-optimized pre-compiled packages (hosted @ openpandora.org)
  • Slapt-get and gslapt for easy installation of these pre-compiled packages
  • An automatized package building system (sbopkg)
  • Three optional standard firewall configs for eth0, usb0 and wlan0
  • Other optional firewall configs for routing/firewalling
  • Kernel recompilation made easy
  • Updates through official Slackware repository
  • The SL4P build system (hosted @ openpandora.org), which can be used to port any Linux/*NIX to Open Pandora
  • Official OP 3.X kernel + realtime kernel
  • Optimized Notaz's SDL
  • Bsp's c64-tools for the DSP
  • Glshim from Lunixbochs
  • Gl4es and SDL2 from ptitSeb
  • Gcc, make, perl, python2, python3, ruby, OpenJDK, SFML, etc.

Helping this project

  • Please consider making a donation.
  • This will help the SL4P project, and also the whole Pandora community, as part of it funds pre-orders.
  • To do so, go to PayPal, log in and click on "Send Money". Donate to donation@openpandora.org and indicate in the PayPal comment field that you are donating for the Slackware project. Then PM me, so I will include you in my thx list ;^).

Older releases Wiki pages

  • To keep this front page clean for the most recent release - 14.2 -, I moved previous versions elsewhere.
  • The old page for the 14.1 release is located here.
  • The old page for the 14.0 release is located here.
  • The old page for the 13.37 release is located here.

OS architecture

  • 14.2 is the last and final ARMv5te, little endian, software float ("soft-float", "armel"), EABI.
  • 14.2 has the armhf compatibility layer, therefore can run some armhf programs.
  • -current is ARMv7-a, little endian, hardware float ("hard-float", "armhf"), EABI, therefore not compatible with most .pnd .

Stable or -current ?

  • Stable is for production use, ie. for work, as a server etc..
  • -current is a work in progress. Although it's pretty usable, some things may be broken/unstable.
  • -current rootfs may be smaller or bigger from build to build, as I can include or remove KDE, amongst other things.
  • If you want to help the development, I prefer that you use -current.
  • And finally, -current repository may be empty. It's because a new stable release is out.

A word about SOLEIL

  • SOLEIL is another project of mine, based on SL4P.
  • It's basically the same OS from the Pandora point of view, but has some neat extended features. Feel free to take a look at it.

A word about security

  • The shipped MPlayer is optimized, but outdated, if this is a concern, you can uninstall it and use the official Slackware up-to-date version instead.
  • Same applies for bluez, but note that there's no working up-to-date OP-compatible working package.
  • See also #Firefox, Thunderbird, SeaMonkey and Java-OpenJRE/JDK updates
  • SL4P's Bluetooth may be vulnerable to this exploit.

Media choice

Installation

Note: if you're a Linux noob, and you're scared by this Wiki page, check this simple tutorial from F_Slim. Thanks to him.
Note: if you are one of the last windows users, you can install SL4P using the method nicely provided by ingoreis. Check this thread.

  • Format a 8G or more SD card with the Ext4 filesystem. To make explanations clear, name it SLACK.
  • You can disable the Ext4 journal to get a better performance, with the sdc1 partition for example:
tune2fs -O ^has_journal /dev/sdc1
  • Note that Ext4 support is enabled since SuperZaxxon v1.75 firmware, so be sure to update. If you don't/can't, you can safely use Ext2 instead.
  • If you don't know how to format a drive, use GParted under Linux, or run their Live-CD. Here's the manual.
  • It's highly recommended to have a second partition formated as a swap. 256M or more is a good choice. 512M is wiser is you plan to compile some stuff, or for server use.
  • If you don't plan to use this partition configuration (OS followed by swap), you'll have to edit the /etc/fstab after having uncompressed the rootfs.
  • If you're cleaning up a previous SL4P installation for a fresh new one, proceed like this:
rm -rf /media/SLACK/*
rm -rf /media/SLACK/.cache/
rm -rf /media/SLACK/.keepdir/
rm -rf /media/SLACK/.splash/
rm -rf /media/SLACK/.subversion/
rm -rf /media/SLACK/.Trash-0/

then unmount, fsck and sync before plugging back the card.

  • To do this, get the SD device name:
cat /proc/mounts

You will see something like:

/dev/sdc1 /media/SLACK ext2
  • Unmount the partition:
umount /media/SLACK/

then check the partition with fsck

fsck -y /dev/sdc1

and sync:

sync
  • Grab the latest 14.2 rootfs here.

Or

  • Grab the latest -current (unstable) rootfs here. The -current repository may be empty. It's because a new stable release is out.
  • Plug back the SD card to remount it.
  • Uncompress the rootfs on your SD. Be root, using su -, or sudo:
sudo tar jxvfp SL4P-[version]-[build].tar.bz2 -C /media/SLACK/ --numeric-owner

First run

  • Be sure your Pandora's clock is set. Otherwise, your filesystem will be checked.
  • Power down your Pandora, insert the SD card in the left slot (also called slot 1), and power on your unit.
  • If you're prompted to enter the root password for maintenance or to type Ctrl-D, just wait, the unit will restart and check the filesystem automatically.
  • You will be prompted to choose a password for the root user.
  • You will be prompted to create an user. At some explicit point, push [up] to put this user in adequate groups.
  • Then you'll be driven to the log in screen. Do not log in as the root user
Bug: very unlikely to happen, but when using startx (not the SL4P default setup), you can be blocked at a black screen.
Use pandora button + power to reboot.

Autologin

  • The slim login manager, which is SL4P's default, can automatically log in an user. You're asked about it at the first login. Else, edit /etc/slim.conf to change the configuration.
  • KDM works, but is too heavy. You have to edit /etc/rc.d/rc.4 in order to use it.

Basic usage

  • In order to type commands as root, you have to type su -. You can use just su, but I don't recommend it because you won't have the full root environment.
  • To choose a window manager, type xwmconfig.
  • I ship those:
Xfce
fluxbox
blackbox
WindowMaker
twm
9wm
enlightenment17
jwm
minimenu
openbox
wmii
  • In some -current or -RC builds, i ship KDE. Avoid selecting it as full desktop on 256M Pandora.
  • To power off, or reboot your Pandora when not in Xfce and its user-friendly menus, become root with:
su -

and type:

halt

or

reboot

Setting up your timezone

  • Become root and use
timeconfig

Setting up your language

  • You can set your locale pretty easily. First, you have to know which languages are available, type:
locale -a
  • Choose the one that best suits your need. I highly recommend to use the versions with .utf8 .
  • Then be root and edit /etc/profile.d/lang.sh .
su -
emacs /etc/profile.d/lang.sh
  • You'll have to change this variable with the one you need:
export LANG=en_US.UTF-8
  • Save the file, make sure it's executable:
chmod +x /etc/profile.d/lang.sh
  • Reboot.

Services started at boot

  • To enable or disable services at boot, become root, then type pkgtool, then go in setup -> services, check the option with space then push enter.
  • Some services are not listed here. For example, to activate the NFS server permanently, tweak /etc/exports and /etc/hosts.allow, then:
 chmod +x /etc/rc.d/rc.nfsd
 /etc/rc.d/rc.nfsd start (not needed after a reboot)

Installing a program - Tools

  • Slackware archives are .tgz or .txz .
  • Slackware uses three powerful tools: installpkg, removepkg and upgradepkg.
  • A fourth tool named makepkg build packages from compiled sources.

Installing a program from source

sbopkg -r
  • The sync may take some time. Once you've done that, run
sh /root/sboflags.sh

to optimize the builds for the Pandora. You have to run this script after every sync.

  • Then all is set up, you just have to use
sbopkg

and choose "Local SlackBuild" when prompted.

  • When the job is done, remove useless files to save disk space:
rm -rf /tmp/SBo/*
rm -rf /var/cache/sbopkg/*
  • Note that Slackware does not check dependencies, so you have to get the right build orders looking here: http://slackbuilds.org/
  • To check if some of the dependencies are already installed in your system, look in /var/log/packages/ . For example, libgnomecanvas:
ls /var/log/packages/libgnomecanvas*
  • Also note that gnome libraries must be compiled in a certain order. I already did the job, and shipped them in the rootfs.
  • If you don't use a SlackBuild script, then the Slackware procedure almost always ends like:
make install DESTDIR=/tmp/whatever/
cd /tmp/whatever/
makepkg /tmp/whatever-1.0.0-arm-1.tgz
installpkg /tmp/whatever-1.0.0-arm-1.tgz
  • If checking and fixing all of those pesky dependencies manually is too much of a burden for you to bear: fear not! Sqg (slackbuilds queue generator) saves your day!

Installing a program with a precompiled archive

  • I compiled a lot (450+) of packages from http://slackbuilds.org/.
  • I shipped a graphical install tool named GSlapt. Launch it with its icon, update the package list, then install what you need, checking the dependencies of your programs here: http://slackbuilds.org/
  • You can also proceed manually. Find 14.2 packages here, and -current ones here.
  • Download what you need, checking the dependencies of your programs here: http://slackbuilds.org/
  • Put all needed .tgz or .txz in a folder, go root using su -, then type:
installpkg /path/to/your/folder/*.t?z
  • Please report any non-working package.

About SL4P precompiled archives

  • All shipped and extra archives are compiled with sbopkg with Pandora-optimized flags.
-DPANDORA -O2 -pipe -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fPIC
  • The links to the sources are located here: http://slackbuilds.org/repository/
  • The building order is fixed in queue files, kind of build playlist.
  • The queues are located in /var/lib/sbopkg/queues/
  • About shipped archives (base and base-more), you don't need to download them as they're already in the rootfs, see this.
  • Some archives won't work, like Kompozer, because it's a repackaging of x86 binaries. As I'm not yet in the process of fine-tuning, I left them for now.

Installing KDE 4

  • Plug the net, become root using su -, then type:
slackpkg update
slackpkg install kde
  • Note that although i already slimmed down KDE configuration files for less eye-candy, a 512M Pandora is recommended to run the full desktop.
  • Anyway, you can run any KDE application (konqueror, kwrite...) flawlessly with the 256M version running Xfce.
  • Type xwmconfig to select KDE, or any other window manager.

Updates

slackpkg update
slackpkg upgrade-all
  • Do not use slackpkg when using a -current. Instead, look at the changelog, download packages from here, become root using su -, then type:
upgradepkg /path/to/the/updates/*.t?z

Note that some packages like a/aaa_elflibs are not supposed to be upgraded in -current. A new rootfs is needed.

  • You can eventually set up a cronjob. In this case, check /etc/slackpkg/blacklist to ensure some critical packages (e.g. kernel) will not be updated.
  • Slackware usually provides updates during 10+ years, but it seems to be less with Slackware ARM. See the news for more details.

SL4P-specific updates

  • I provide Pandora fixes, available as Slackware archives.
  • Simply use GSlapt, and update.

Firefox, Thunderbird, SeaMonkey and Java-OpenJRE/JDK updates

  • Slackware ARM 14.2 doesn't provide anymore updates for Firefox, Thunderbird and SeaMonkey because of a build problem.
  • You have to download the unsupported -current archives and update them manually, using the method mentioned above.
  • Get them here.
  • About Java-OpenJRE/JDK, it's not possible to update them through slackpkg because it was added on-the-fly to Slackware ARM.
  • Check and get the updates here.
  • Be sure to download and update both as the jre is not included in the jdk.

Kernel updates

  • I provide kernel updates through GSlapt.
  • Many kernels are already available in the rootfs, like real time, or non-debug.
  • To know which kernel is currently running, type:
uname -r
  • To enable a new kernel, for example 3.2.30-szfinal or the 3.2.26-rt, do:
cd /boot
rm uImage
cp uImage-3.2.30-szfinal uImage

or:

cd /boot
rm uImage
cp uImage-3.2.26-rt uImage

And reboot.

  • If lsmod reports that no modules are loaded (that means, eg., no touchscreen), then run as root:
depmod -a

And reboot again.

Automounting a SD card or an USB drive

  • No system-wide automounter is enabled for now.
  • Only Xfce and some other window managers do automount.
  • As Xfce mounts devices at insertion, if you booted with a second SD card or an USB drive plugged in, you have to click on the device icon.
  • If you plan to use Minimenu, you currently have to automount under Xfce, run xwmconfig, then log out to run Minimenu. This is the best method to save RAM.
  • You can also launch Minimenu under Xfce. Open a terminal and type:
mmwrapper -fmmenu

USB at boot, suspend and powersaving

  • Usually, you have to click on the Xfce "Toggle USB Host" icon whenever you need USB support.
  • I disabled the USB support by default. As said Notaz, it "Uses around 3x more power when idle, fails to suspend properly.".
  • If you want to enable USB host and USB networking support at boot, be root and edit /etc/rc.d/rc.local .

Near the top, change

#modprobe ehci-hcd

into:

modprobe ehci-hcd

Fixing the endless reboot

  • Be sure your Pandora's clock is set. Boot Official Pandora OS on the NAND, and check/set time.
  • Boot SL4P, when prompted to enter the root password for maintenance, do it, then type:
fsck -y /dev/mmcblk0p1
  • You can do the same under Zaxxon. Note that it will be /dev/mmcblk1p1 if SL4P is on a second card.
  • You will be warned if the card is still mounted, so unmount it, and proceed.

Changing the Hostname

Switching from 1GHz to 600MHz Pandora

  • I slightly modified the clock script to split the parameters into two categories: 1Ghz and 600MHz.
  • You can safely put SL4P in any OP, and have a max OPP + max MHz settings for each as the model is recognized at boot, then clocked.
  • It's totally transparent, just set your parameters as usual.

Fast boot tweak

  • I moved some of the boot stuff (ldconfig, font cache, mime database) in /etc/rc.d/rc.local_shutdown.
  • The reboot/power off process is slowered, but the OS integrity is safe.

Bluetooth audio

  • SL4P already has everything you need. Don't even start with pulseaudio (unless you really need to)!

Proper Bluetooth configuration

  • We need to enable access to the BT protocols we want to use:
  • Fix /etc/bluetooth/audio.conf with:
[General]
Enable=Source,Sink,Headset,Socket,Control

Find your BT device's MAC address

  • Enable Bluetooth on your pandora.
  • If the BT device manager doesn't pop up automatically, start it with:
blueman-manager
  • Make sure your device can be found (i.e. is not paired with another computer or mobile phone etc.)!
  • Search for your device and find it's MAC address.
  • Don't connect to/pair with your device yet!

Proper ALSA configuration

  • We will define a new bluetooth device and route all ALSA traffic through it.
  • This means your BT device will be the default ALSA output device!
  • Fix ~/.asoundrc with your MAC address:
pcm.btheadset {
type plug
slave {
pcm {
type bluetooth
device "[ADD MAC HERE]"
profile "auto"
}
}

hint {
show on
description "BT Headset"
}
}

ctl.btheadset {
type bluetooth
}
  • Fix /etc/asound.conf with your MAC address:
pcm.!default {
type bluetooth
device "[ADD MAC HERE]"
}
  • Reboot and pair with your device using the A2DP protocol.
  • Enjoy BT audio with your Slackware and your Pandora :)

SGX drivers installer

  • With notaz's blessing, i tweaked his SGX drivers installer to make it work both under SL4P and Zaxxon.
  • Get it here.
  • You can safely remove your old version.

PND compatibility list

  • SL4P supports .pnd files.
  • PNDs used to be recognized automatically. It's not the case anymore, and I don't know why.
  • So here's the workaround: after the insertion of your SD or USB drive, you have to push the green button near the Xfce menu.
  • Due to 3.2 kernel and dynamically linked libraries, not all .pnd are compatible.
  • If a pnd doesn't work, first thing to check is its log file in /tmp .
  • View the PND compatibility list here.

Advanced usage

  • I wrote some tutorials to do interesting things.
  • All those guides are applicable to any version of Slackware, ie. x86, x86_64, IBM mainframe, etc.
  • Follow this link.

Sources

Build system

  • I distribute it under the GPL 3 license.
  • It may look a bit messy for now (and indeed, some part have to be cleaned), but it's versatile, as I intended from the start.
  • It's mainly three bash scripts.
  • You need a Pandora to run the third one.
  • Depending on what you comment/uncomment, you can produce an alpha build, very minimal, or a full build.
  • Depending on what you edit, you can use it to port any *NIX to Open Pandora, and maintain your build very easily.
  • Get it here, along the more detailed instructions.

FAQ

Ask a question/Report a bug

  • You're welcome to do so, and please post here or here.