Hi ,


This is my first post on this forum. I have system level
programming experience on Nonstop platform. I am trying to get insight into linux OS


I was trying to install systemtap rpm. For which I required three rpms.

1. Kernel
2. Kernel-debuginfo
3. kernel-devel

But, then I had a kernel version kernel-2.6.11-1.1369_FC4.i586.rpm for which kernel-debuginfo RPM was not available. So i upgraded the kernel rpm to kernel-2.6.17-1.2143_FC4.i686.rpm . Now this kernel installation did not show any dependency issues.

When i boot the kernel with runlevel 5. X windows system doesnot start and after the initial kernel boot, screen blanks out.

So I tried booting the system with runlevel 3. Boot happened successfully and I could log into the system.
but again when i tried starting X windows, screen blanks out.

I dont know what is the problem here with X windows. I am not able to figure it out. Can anybody please solve this issue.

- adil

I don't recall ever having a kernel upgrade bork the xserver.
Have you tried to run the command: system-config-display ?

On my FC5 box, when I use the nvidia drivers, I get that black screen until I edit the /etc/X11/xorg.conf monitor section ....

Thanks for the quick response.
Well I am not much aware in this regard. But, I dont think i have changed any drivers. Could you please explain how my upgrading the kernel may have led to this
issue?

Secondly, Is there any method by which i can make the X windows go into verbose mode so that I can see its progress while starting up. It can help me exactly pinpoint the problem. Also, If there is any logfile created by X windows system which might suggest the problem. Currently I am clueless about the problem.

The logfiles of x windows are situated in /var/log (where all logfiles should be). There names start with Xorg. Just look at the most recent one.

B.T.W. What videocard do you have?

When you upgrade the linux-kernel you have to reinstall the gfx-card drivers. I know this sucks, but just have a look in /lib/modules and you see why; there are seperate directory-trees for every kernel-version installed. When you install drivers they are installed into the kernel-directry-tree of the currently running kernel-version and are not automaticaly copied to a newer kernel-version.

run the command
system-config-display --reconfig
this way you will reconfigure the X.

do you have an nvidia video card? (probably ati also) If you do, you will have to re-install the proprietary drivers. This will happen anytime you upgrade the kernel.

1.
I dont dunno what is my driver type ... may be the
following command output will let you know about that

[tcs@linuxsvr video]$ pwd
/lib/modules/2.4.20-8/kernel/drivers/video
[tcs@linuxsvr video]$ ls
aty fbcon-mfb.o matrox pm3fb.o sstfb.o
aty128fb.o fbcon-vga-planes.o mdacon.o radeonfb.o tdfxfb.o
clgenfb.o fbgen.o neofb.o riva vga16fb.o
fbcon-hga.o hgafb.o pm2fb.o sis
[tcs@linuxsvr video]$


2.

system-config-display --reconfig

the above command again gives me a blank screen.


3.

I have updated my kernel. so i dont have previous kernel
directory under /lib/modules directory structure.

I think that there is some problem with x11-drm
I have read on some forum that while switching kernels
x11-drm needs to be merged again.

If it is so, could anybody tell me what is that and
what is the procedure for doing that?

This is the error in my Xorg.0.log
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed

I further found that the kernel might not have
any drm module loaded

dmesg | grep drm doesnot show anything

Can anybody tell me how to build drm modules and load
them into kernel.

I think this issue is pretty common in the last day or so

http://www.linuxformat.co.uk/index.p...ewtopic&t=4050

"I have updated my kernel. so i dont have previous kernel
directory under /lib/modules directory structure."



Here's one sound advice: always keep your previous kernel,
so if things do not work you can always boot into the last
working one...