SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm excited to join the Slacking community. After several years of migrating from Windows to Ubuntu (and finding myself totally reliant on apt-get), I've decided to complete the commitment to better operating systems and delve into Slackware.
That said, I've successfully installed Slackware on an old HP laptop. Had some trouble with LILO and (an existing copy of) GRUB fighting, so I ended up nuking the drive with dd and then reinstalling. Everything went smoothly after that and I'm left with a surprisingly crisp and snappy system.
Onward, to the problem:
I chose Fluxbox as my default window manager, and it worked swell. Then I decided that I really wanted Openbox instead. So I got it from slackbuilds, compiled, and installed it. I then updated my .xinitrc file to reflect the change.
Now, I have what feels like a 50/50 chance of the laptop booting up to a login prompt. The other half of the time, it begins booting, and then right when it would normally flicker, and come back with smaller, cleaner text, it goes blank. The backlight is on, but the screen is black. Furthermore, I can still log in after waiting a reasonable amount of time and blindly entering my name and pass, then I can execute 'startx' and openbox successfully launches.
Once in openbox, I can use ctrl-alt-bkspc to close the window manager, and end up with a working shell, what I expect to get on initial boot.
I'm willing to upload any configuration files that may be pertinent, or even a video of it booting, please let me know what I should include.
All in all, it would be pretty straightforward to re-install, but I'd like to at least try fixing the problem first, otherwise I won't learn anything.
It seems weird to mention .xinitrc and then not include it, so I've copied off the computer. Here it is.
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
# merge in defaults and keymaps
[ -f $sysresources ] && /usr/bin/xrdb -merge $sysresources
[ -f $sysmodmap ] && /usr/bin/xmodmap $sysmodmap
[ -f $userresources ] && /usr/bin/xrdb -merge $userresources
[ -f $usermodmap ] && /usr/bin/xmodmap $usermodmap
# Create default user directory & populate it if not already existent
if [ ! -d $HOME/.config/openbox ]; then
mkdir -p $HOME/.config/openbox
cat /etc/xdg/openbox/menu.xml > $HOME/.config/openbox/menu.xml
cat /etc/xdg/openbox/rc.xml > $HOME/.config/openbox/rc.xml
# Not sure what I'm doing, going to open xcompmgr
# Desktop background
feh --bg-center /home/ctag/wallpaper/space-ship.jpg
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
exec ck-launch-session dbus-launch --exit-with-session openbox
# xcompmgr &
Thanks for reading,
Last edited by ctag; 07-13-2013 at 12:02 AM.
Reason: added .xinitrc
If you haven't done all the patches, the easy way is to create a directory in /usr/local
mkdir -p /usr/local/patches
# use this one for 32-bit
# use this one for 64-bt
<wait a while>
That will bring system software up to the current stable level (be sure to use either the 32-bit or the 64-bit line above, don't do both).
Now the kernel. The kernel should be at 3.2.45. You're still in /usr/local/patches, so
# use this for 32-bit
# use this for 64-bit
<wait a while>
upgradepkg --reinstall *.t?z
You must run lilo. Look at /etc/lilo.conf, down at the bottom it should look like this:
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
# Linux bootable partition config ends
Yours may vary a little, perhaps the root partition, but if you installed the default system, that's pretty much what it's going to look like.
Then you can reboot -- all the above brings your system to the current stable level.
Note that when you upgrade the kernel it's going to take while (well, all the above upgrades are going to take a while truth be known) -- minutes, not hours, but maybe quite a few minutes, don't worry about that.
All the above assumes that you installed default Slackware and have not done a custom kernel (where you compiled the kernel yourself). There are other ways to get the patches and apply them but the above is easy and fast (depending on your Internet connection speed, of course) and gets you up to date quickly.
May be it is a video prblem.
Did you check any log or message files?
There should be something there...
May be i am a little newbie but donīt understand exactly if you enter fluxbox directly from booting.
so I ended up nuking the drive
Excellent! Iīd never heard that expression before.
I'm not sure where to check for an error or message log. I have Slack set to boot to a terminal (it's default, I believe) from which I can log into either root or my regular account and then load openbox if I want a desktop.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
There was a glitch in one or two copies of the 3.2.45 kernel (having to do with black screen with Intel graphics); the version at osuosl.org is the current, working, one and it won't hurt to do the upgradepkg --reinstall *.t?z just to make sure. The symptoms were when the switch is made during boot, the screen goes black.
It could also be a hardware problem but I'd do the software first then dig into the hardware (might be as simple as a pinched cable or loose connector, but then...).
I have this same problem, except I'm using Radeon HD 6480G Graphics.
When it hits the framebuffer during boot I get the black screen or sometimes I get a bar code screen, when (if) it come back in it come in around DRM or bluetooth. I am up to date with 64-14 stable. So...
Would like to see more feedback on this subject.
Last edited by r.vaillancourt; 07-14-2013 at 11:27 AM.