Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.

Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.

If you want to support my work, please consider a small donation:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
slackware:fixes [2006/04/14 14:06] – alienslackware:fixes [2006/09/29 20:27] – Shift-PageUp explained alien
Line 22: Line 22:
 ---------------- ----------------
  
 +==== ALSA OSS sequencer not loaded ====
 +
 +In Slackware 10.2, the ALSA OSS-compatible sequencer module is not loaded. This results in missing device files ''/dev/midi'' and ''/dev/sequencer''.\\
 +Edit the file ''/etc/rc.d/rc.alsa'' and look for the function <code>
 +load_alsa_oss_modules() {
 +  if ! cat /proc/modules | grep -wq snd-pcm-oss ; then
 +    if ! cat /proc/modules | grep -wq snd_pcm_oss ; then
 +      echo "Loading OSS compatibility modules for ALSA."
 +      modprobe snd-pcm-oss
 +      modprobe snd-mixer-oss
 +}</code> Add the following line after the line ''modprobe snd-mixer-oss'' in that function: <code>
 +      modprobe snd-seq-oss
 +</code> and restart ALSA.
 +
 +----------------
 +
 +==== Using Samba without installing CUPS ====
 +
 +In Slackware, CUPS is available as the default printing solution, while the old lprNG remains in the "''/pasture''" directory. Some people still prefer the trusted lpr/lpd style of printing and do not install CUPS. However, the Samba package is compiled against the CUPS libraries. Although the necessary CUPS libraries are always installed with the //aaa_elflibs// package, Samba still periodically complains loudly in the ''/var/log/messages'' logfile about the absent CUPS server: <file>
 +smbd[....]: Unable to connect to CUPS server localhost - Connection refused
 +</file>
 +The solution (if you don't need a printing facility in Samba) is to disable printing completely. This is what you need to add to the **''[Global]''** section of your ''/etc/samba/smb.conf'' file: <code>
 +load printers = no
 +printing = bsd
 +printcap name = /dev/null
 +</code>
 +
 +----------------
 +
 +==== Where is mkfs.vfat? ====
 +
 +FAT32 (also known as vfat) partitions are commonly used on USB sticks, and they are also quite useful when you have a dual-boot system with Windows on a NTFS partition on the "other side", and want a shared partition where both OS-es can write files.\\
 +Now, where did that "''mkfs.vfat''" command go, that seems to be available on so many other Linux distributions and is mentioned in lots of Google search results when you try to find out how to format your partition as FAT32 instead of FAT16?
 +
 +The ''mkdosfs'' command aka the ''mkfs.msdos'' command (they're the same command, one is symlinked to the other) which by default creates FAT16 ("//DOS//") partitions, can create these FAT32 partitions as well!\\ Run it with the **''-F32''** switch: <code>
 +mkfs.msdos -F32 /dev/<devicename>
 +</code>
 +
 +----------------
 +
 +==== The bootup messages scroll off my screen too fast ====
 +
 +When your Linux kernel boots, it spits out all kinds of informative messages. When the Slackware init scripts start, you'll get even more messages that scroll across your screen. The kernel logs its messages in a ring buffer that you can display (after login) with the command <code>dmesg</code> If you wait too long with that command, the kernel messages that are logged after the initial boot will erase the beginning of the buffer (it has a limited capacity). You can still read the initial buffer content at your leisure though: it is saved by Slackware in the file ''/var/log/dmesg''.
 +
 +Still, not all of the standard output and standard error from the init scripts is logged to disk. Only when the syslogger is started, will the scripts start logging to ''/var/log/messages'', ''/var/log/syslog'' etc... but you easily miss information if you for instance have a hardware problem. The text scrolls off the screen so quickly that you usually can't properly analyze it (unless your hardware is terribly slow :-)).
 +
 +One trick can save the day: when your computer finsishes booting up and displays the login prompt, you can scroll back by pressing the key combination <key>Shift</key> <key>Page Up</key> repeatedly!\\ You need to use a VESA console though, and not have your system configured for graphical login (runlevel 4).

Trace:

Fixes for annoyances in Slackware ()
SlackDocs