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.
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
X Server Doesn't Start
My Slackware 11 install was running just fine.
I rebooted into WinXP and then back to Slackware. Now suddenly it has stopped working. when I do startx.. It shows fatal error 0 compatible screens found. That a screen was found but it is not supported. I tried to copy the log file to my VFAt partition but it is unable to mount it saying "error unknown file system NTFS"
Well on Slack there are allway easyer ways to walk foot by foot :-/
mount the source of your distro (the DVD) and go type:
(mc *is* your friend)
navigate to the mountpoint (usually /mnt/cdrom)
navigate to slackware/testing (or elsewhere) where the modules of 18.104.22.168 reside...
point to the *.tgz package containing the modules...
press [F2] for user menu
press @ (do something...)
type 'installpkg' and hit [enter]
(that whas it)
soon you will have the modules installed...
of course there are other ways... :-)
well in the packages there are:
but to get the modules onboard you need the module-package only.
Once the kernel is loaded, modules depmod-ed you do everything left...
is the 'midnight-commander' a northon-commander clone for POSIX-systems.
It's my best friend in shell. Try it: just type 'mc' and hit [enter]:-)
Yap, when faring with LILO you have to lilo many times (just can't overdo)
But me faring with GRUB, had to grub once, later only fare, one grub is more than 'nough.
I like grub better, since I allways fiddle and tamper and then break stuff.
Grub's MBR alone supports a shell and all sorts of spicy stuff, grub's boot stages support filesystems and the grub itself has a built in shell also, so once i make someting foolish i just re-edit the kernel's commandline in grub's menu and off I go.
Lilo has better graphics, better support for troublesome BIOS-es and so on, but Grub is by far more flexible and powerful for emergency cases. With grub you could even boot a kernel form say: /usr/src/linux/arch/i386/piggy/bzImage [from the boot-prompt] if You can't find any better one