LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   After a fresh install, X.org suite completely unresponsive (http://www.linuxquestions.org/questions/slackware-installation-40/after-a-fresh-install-x-org-suite-completely-unresponsive-775009/)

N1GHTS 12-11-2009 02:23 PM

After a fresh install, X.org suite completely unresponsive
 
User Experience Level:
Beginner to Medium
Target Computer:
HP ProLiant DL145 Rack-mount server
System Specs:
Single SCSI 75GB HD, 2 AMD 64-bit Opteron's, 16 GB RAM
OS Version:
Very latest stable Slackware v13 64-bit installed from DVD image

Background:
I am an experienced professional software architect with previous experience installing Slackware on at least two other computers in the past. I primarily work with Windows but am dying to transition to Linux. My job right now is to install the latest build of my favorite server distro onto this HP DL145 server. However, its been a long time since I've installed it, and I've forgotten quite a bit of basics on setting up Linux.

Process:
I used the HTML-based manual provided on the Slackware website to guide me through the installation process. I opted to create various partitions useful for the role this server will play, and chose the best file systems for the jobs of those partitions. I installed the default packages and used automatic installation (full installation) for each of the default packages. Finally I created a password for the root user. Everything went perfectly fine. After a reboot, everything looks good. Network works (used links to test it), mouse works...

I then mounted my DVD, copied the kernel from the /kernels/huge.s folder into the correct /boot folders, and ran /sbin/lilo as per the instructions.

Problem:
When I type "xorgconfig", i get "Command not found". But that's not the biggest problem. When I type "xorgsetup", nothing happens. It takes me immediately back to the prompt, almost as if I had typed nothing in the command prompt at all. Ive tried "Xorg", "Xorg -configure", "Xorg --help", "xorgsetup --help", all of these commands appear to do the same thing. They do nothing and the cursor blinks at the next line after the command I typed.


Any help is appreciated.

allend 12-11-2009 05:50 PM

From CHANGES_AND_HINTS.TXT
Quote:

Speaking of Xorg, the version of Xorg shipped with Slackware 13.0 will not
(in most cases) require an /etc/X11/xorg.conf file at all. Configuration of
input devices and such is handled by HAL, and the X server autoconfigures
everything else. You can still create an xorg.conf file if you wish, or you
can create a minimal xorg.conf with only the specific contents that you wish
to override (as an example, to use a binary-only video driver).
Due to removed drivers and other such changes, it's quite possible that your
old xorg.conf will not work correctly with this version of Xorg.
As root, 'X -configure' will generate the xorg.conf that is being autoconfigured.

N1GHTS 12-11-2009 06:32 PM

Thank you for your reply.

I'm glad that it auto-configures the X config file.


This is what happens when i try to use "exec startkde".

Code:

root@svr:~# exec startkde
kcheckrunning: error while loading shared libraries: libSM.so.6: cannot open sha
red object file: No such file or directory
kapplymousetheme: error while loading shared libraries: libXrender.so.1: cannot
open shared libraries: libSM.so.6: cannot open shared o
bject file: No such file or directory
ksplashx: error while loading shared libraries: libSM.so.6: cannot open shared o
bject file: No such file or directory
startkde: Starting up...
dbus-launch: error while loading shared libraries: libSM.so.6: cannot open share
d object file: No such file or directory
startkde: Could not start D-Bus. Check your installation.


Welcome to Linux 2.6.29.6 (tty2)

svr login: _


allend 12-11-2009 06:55 PM

Try 'startx' instead of 'exec startkde'.
By default, 'startx' will start KDE. Use 'xwmconfig' to use another desktop environment.

N1GHTS 12-11-2009 09:02 PM

Quote:

Originally Posted by allend (Post 3788404)
Try 'startx' instead of 'exec startkde'.
By default, 'startx' will start KDE. Use 'xwmconfig' to use another desktop environment.

On a fresh reboot, this is what my console looks like when I type in any of your commands:

Code:

Welcome to Linux 2.6.29.6 (tty2)

svr login: root
Password:
Linux 2.6.29.6.
You have mail.
root@svr:~# startx
root@svr:~# xwmconfig
root@svr:~# _

What you see there is exactly what I see, and literally nothing happens. It instantly goes to the next line with no errors or warnings or delay. Its as if the operating system is ignoring the execution of any program relating to X.org.

This is the core problem and I have no idea what I did wrong in the installation. Please think of something else I could try.

allend 12-12-2009 07:02 AM

Quote:

I then mounted my DVD, copied the kernel from the /kernels/huge.s folder into the correct /boot folders, and ran /sbin/lilo as per the instructions.
At the end of installation and after reboot you would have had the kernel-huge-2.6.29.6-x86_64 kernel installed. The above would then have overwritten the working kernel.

The easiest solution is probably to conduct a fresh install.

Then to change to the kernel-generic-2.6.29.6-x86_64 kernel ( from CHANGES_AND_HINTS.TXT )
Quote:

Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd.
TIP: /usr/share/mkinitrd/mkinitrd_command_generator.sh is a utility in Slackware 13 that will output a suitable line for mkinitrd.

onebuck 12-12-2009 07:14 AM

Hi,

Quote:

Originally Posted by N1GHTS (Post 3788142)
<snip>
I then mounted my DVD, copied the kernel from the /kernels/huge.s folder into the correct /boot folders, and ran /sbin/lilo as per the instructions.

Problem:
When I type "xorgconfig", i get "Command not found". But that's not the biggest problem. When I type "xorgsetup", nothing happens. It takes me immediately back to the prompt, almost as if I had typed nothing in the command prompt at all. Ive tried "Xorg", "Xorg -configure", "Xorg --help", "xorgsetup --help", all of these commands appear to do the same thing. They do nothing and the cursor blinks at the next line after the command I typed.


Any help is appreciated.

What is your reason for moving a copy of 'huge.s' to boot? The 'generic' kernel would be the one to use daily not a installer kernel.

Your install should have '/boot/vmlinuz-generic-2.6.29.6' that could be used. You will need to create a 'initrd'. Look at '/boot/README.initrd' to see how.

:hattip:

Didier Spaier 12-12-2009 07:22 AM

Your installation is not full. You are missing at least libSM.so.6 which is part of libSM package (X library).

As you could miss many other packages you'll be better off reinstalling from scratch, IMHO.

Make a full install of all packages in all categories (but the kdei category if you don't need it).

And better follow the Slackware-HOWTO file at the root of the DVD than the (slighthly outdated) Slackware book.

Other text files in the root directory of the DVD are worth reading too.

[EDIT] If you don't bother to reinstall, instead use installpkg (as root) to complete your installation:
Code:

installpkg /path/to/DVD/slackware64/*/*txz
This will install all packages in the slackware64 directory.

Afterwards, use slackpkg to grab all upgrades following safety advisories (see man slackpkg). Be careful to uncomment only one mirror for Slackware64-13.0 before running as root:
Code:

slackpkg update
slackpkg upgrade-all

HTH,

N1GHTS 12-16-2009 10:55 AM

I was able to get X to work on Slackware by repartitioning the root from 4GB to 10GB and reinstalling the OS.

Interestingly the first 2 times I reinstalled the OS with the 4 GB root partition, it never prompted me about anything to do with X even though I specifically installed that full package and its dependencies, yet when I bumped up the root partition size, now it gives me a prompt at the end of the installation about the X configuration. I believe there was a silent "out of space" error during the setup process which was not brought to my attention, even after the installation was completed 'successfully'. This could possibly be a bug with the package installer in the setup utility.

Thank you all for your help with my problem.


All times are GMT -5. The time now is 08:03 AM.