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

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


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

Link to this comparison view

slackware:fixes [2006/09/29 19:58]
alien Create a FAT32 partition.
slackware:fixes [2008/11/18 16:00] (current)
alien Explain about HAL related mount error
Line 59: Line 59:
 mkfs.msdos -F32 /dev/<devicename> mkfs.msdos -F32 /dev/<devicename>
 </code> </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).
 +==== "A security policy in place prevents this sender ..." error ====
 +With Slackware 12.0 and onwards, when you are running X Window, and are greeted by the following message when you insert a CD, DVD, or USB stick into the computer: <note warning>
 +A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
 +</note> this means that you need to add your user account to the //plugdev// group.\\ 
 +The command to add your account (for example account called //"alien"//) to the group //plugdev// is: <code>
 +gpasswd -a alien plugdev</code> You need to logout and login again in order for this change to have effect.\\ 
 +If you start your computer in runlevel 3 (non-graphical boot) and run ''"groups"'' you will notice that your account seems to be part of the //plugdev// group already. This is true in a sense: Slackware adds your account to this group and several others like cdrom, floppy //dynamically// for the duration of your login session. Unfortunately the DBUS/HAL daemons do not use Linux system calls to check your group membership. Instead, they rely on what is written in the ''/etc/group'' file.
 +This HAL related issue is actually explained in the CHANGES_AND_HINTS.TXT file (here is a link to the Slackware 12.1 version of [[http://slackware.osuosl.org/slackware-12.1/CHANGES_AND_HINTS.TXT|CHANGES_AND_HINTS.TXT]]). Highly recommened reading material, that file!

Personal Tools