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"

Any suggestions?

Can You please provide the /var/log/Xorg.0.log
and the /etc/X11/xorg.conf
files, and the output of the (run as root) command
lspci
that could shed some more light to your issue...:-)

Didn't You get the X running by default (the vga or vesa driver)?

And of course You can allways run
xorgconfig
from a console and try Your luck...

I tried doing xorgconfig twice.

The thing is it just refuses to start. I wanted to give a copy of /var/../Xorg.0.log but the problem is I can't use my win Partitions in Linux thats why I can't copy it. I will try doing lspci.

Could You manage somehow to download Slax and run it on Your PC?
It's about 192MB a live-linux and it won't write either to NTFS but could to a flash-disk or floppy, so you would't have to re-type...

Oh My God I am the Biggest ASS in the World.

I wanted to install a newer kernel so I had done :
%installpkg kernel-generic-2.6.18-i486-1.tgz

And then I forgot all about it. Now I restart and its going to the 2.6.18 kernel but it doesn't have anyother files as I haven't done any config.

Any Ideas on how I can fix this? How can I go back to older kernel?Maybe I can boot with the DVD and specify kernel.
Or do setup and just do the configuration all over again.


Maybe I

Well on Slack there are allway easyer ways to walk foot by foot :-/
So:
mount the source of your distro (the DVD) and go type:
mc
(mc *is* your friend)
navigate to the mountpoint (usually /mnt/cdrom)
navigate to slackware/testing (or elsewhere) where the modules of 2.6.18.1 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... :-)

but don't I need to install anything else. I mean how could Installing a new kernel be so easy?
just kernel-modules....tgz
what abt kernel-headers kernel-source etc.?

And what is mc

Thanks
Duryodhan
ashamed at how the first line of the post sounds so like a advert.

well in the packages there are:
kernel-<somewhat>-<some_nr>.tgz
kernel-modules-<smoe_nr>.tgz
kernel-headers-<some_nr>.tgz
kernel-source-<some_nr>.tgz
kernel-source-<whatever>.tar.{gz|bz2}
but to get the modules onboard you need the module-package only.
Once the kernel is loaded, modules depmod-ed you do everything left...

mc

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]:-)

Don't bother, what should then I say 'bout my sign below?

ok I will try out what you said but I still dont understand how only by installing the kernel and modules a new kernel will be loaded whereas there is a looong guide on how to do it in Shilo's Guide.

Well... that is what packages are all about... someone allready having the knowledge about what has to be done, has done it allready for you.

In Slackware packages are a bunch of files placed in the right place... and a install script to do some configuration.

ok
anyways...
I did what you said (pkgtool and all) and then I rebooted.
Now LILO is giving error.
"ENDA is too Big Kernel overlaps LILO"

What I did now was to boot with Slackware DVD and then do "sata.i root=/dev/hdb2 noinitrd ro"
So its all working fine. But what do I do abt LILO?

Will liloconfig work?
And how do I find out which is my present kernel version?

After booting from the CD using "sata.i root=/dev/hdb2 noinitrd ro", try running "lilo" and then reboot to see if that helped.

Eric

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
'nough said.

Hey,
Alien_bob it worked!
Thanks a lot SCerovec.
Could you tell me how do I find out my present kernel version?