New Kernel == No More Xserver

[InvisibleSniper]

Hi again,

Recently I have installed a new kernel:
kernel-image-2.6.8-11-amd64-k8

And now I during the GRUB selection during boot up it shows two kernels, and whenever I boot into the new one it is unable to start the xserver I have tried to reconfigure it using:
dpkg-reconfigure xserver-xfree86
But it still fails to notice any graphics device, my current graphics card is an on-board VGA. My motherboard is MSI K8MM-V.

Thanks Again In Advance.

[antidrugue]

What does

cat /var/log/XFree86.0.log | grep EE

has to say about that?

[InvisibleSniper]

I'll try that command now, I have to write it down and log back out as I am using the 2.4 kernel to reply to this thread. But one thing I would like to update yous on is that the error I get once I try to startx is:

no screens found

[InvisibleSniper]

Sorry for the double post, but I have wanted this post to stand out and not just be an edited post of the previous one. Anyway the results from those commands are as follows:

EE) VESA(0): unknown type(oxffffffff)=0xff
EE)Screen(s) found, but none have a usable configuration.

I would like to also note some more information that could help. The kernel that I used to install the gdm/xserver ect, was 2.4.27-2-386 (32 bit version) and the kernel that I am having trouble with is kernel-image-2.6.8-11-amd64-k8 (64 bit version) could it have anything to do with the 32 to 64 bit change? I was thinking that this is why it is unable to use the configuration (ie becuase it was installed and configured using 32bit)? My processor is an AMD Athlon64 3200+.

[antidrugue]

The kernel that I used to install the gdm/xserver ect, was 2.4.27-2-386 (32 bit version) and the kernel that I am having trouble with is kernel-image-2.6.8-11-amd64-k8 (64 bit version) could it have anything to do with the 32 to 64 bit change?

I don't think so, because this new kernel (kernel-image-2.6.8-11-amd64-k is still compiled in 32 bits, but it is optimized for 64 bits athlon CPUs.

I'll try that command now, I have to write it down and log back out as I am using the 2.4 kernel to reply to this thread

Use a floppy, or a USB key to save the log.

EE) VESA(0): unknown type(oxffffffff)=0xff
EE)Screen(s) found, but none have a usable configuration.

This seems to be a problem with the framebuffer.

As well,

cat /var/log/XFree86.0.log | tail

could be useful.

Or maybe

cat /var/log/XFree86.0.log | grep -i framebuffer

And in your /etc/X11/XF86Config-4, which driver are you using?

[InvisibleSniper]

The driver I am using is "vesa" but I have tried all of the drivers and none of them work. The new commands you gave me basically resulted in the same output apart from the

cat /var/log/XFree86.0.log | grep -i framebuffer

which had no ouput as it was unable to find any information related to that search query. I would like to note on another thing too; I have just taken an Nvidea AGP video card out of my system(before I installed the new kernel) and I was still using the "vesa" driver. I didn't change any xserver settings after I had taken it out, but now I am using an on-board video card.

[antidrugue]

I would like to note on another thing too; I have just taken an Nvidea AGP video card out of my system(before I installed the new kernel) and I was still using the "vesa" driver. I didn't change any xserver settings after I had taken it out, but now I am using an on-board video card.

What is your exact motherboard model? What kind of onboard video is that?

Backup your existing X config

cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.bak

And then try to reconfigure X :

dpkg-reconfigure xserver-xfree86

There should be a more appropriate driver then "vesa", though the generic "vesa" should work.

[InvisibleSniper]

I could not find what intergrated graphics card I have but here is the direct link to the specifications of my board.
http://www.msi.com.tw/program/produc...il.php?UID=647

[antidrugue]

Then the proper video driver would be called "via".

[InvisibleSniper]

I tried VIA instead of VESA on the 2.4.27-2-386 kernel and it couldn't even start X display.

I got the following message:

Not starting X display manager (xdm), it is not the default display manager.

If you have anymore possible sollutions "I'm all ears".

Thanks Again.