New kernel boots with screen problems!

JM11 · 02-15-2007, 10:09 AM

Hi, i jus recompiled the 2.6 kernel in slackware 11 to remove some unrequired modules (just some language support and networking modules) using:

make menuconfig
make
make modules_install

I then copied the image to /boot and configured lilo to boot it.

BUT when i restart and boot the new kernel, the screen continues to fill up with lines!!!!!!!!!!!

I must point out that the old kernel boots using 1024x768 resolution and the new one in a widescreen screen resolution (my laptop is widescreen) for some reason.

Anyone knw what the problem is

H_TeXMeX_H · 02-15-2007, 03:34 PM

Quote:

Originally Posted by JM11

BUT when i restart and boot the new kernel, the screen continues to fill up with lines!!!!!!!!!!!

Can you describe the lines a little more ?

Something like this ?

Code:

______________________________________________
________________________________________________
________________________________________________________
______________________________________
_______________________________________________________________
__________________________________

JM11 · 02-15-2007, 04:37 PM

Well they are horizontal. Like the type u get when tuning a tv i guse.
But this only seems to happen when i compile 2.6 kernel or above. Doesnt happen with 2.4.
Im thinking its to do with the graphics card but not sure. Usually console boots up in 1024x768 so doesnt use the full widescreen. However this type it i using the full screen but filling up with these lines for some reason.

H_TeXMeX_H · 02-15-2007, 05:48 PM

check '/etc/lilo.conf' and make sure 'vga = normal' (remember to run '/sbin/lilo' after changing it) and try again.

bird603568 · 02-15-2007, 11:58 PM

try this:
make
make modules
make modules_install
make install

and if that doesnt work work there has to be something wrong with the kernel

JM11 · 02-16-2007, 03:23 AM

The lilo config was changed and i did run /sbin/lilo straight after editing the lilo.conf file.
I'll give a shot at your're suggestion bird603568, but im not sure its the kernel because it booted fine when i installed slackware with the huge26.s.
Also i downloaded the full source of the 2.6.20 kernel version and compiled that and it gives me the same thing for some reason.

ciotog · 02-17-2007, 01:11 PM

The "make install" command at the end of the steps bird603568 gave will only work if lilo.conf is set up with "/boot/vmlinuz" as one of the boot options. Otherwise there's no reason to use it.
What options to you have in "Device Drivers -> Graphics support" from menuconfig? If you've used an old .config file from a 2.4 series kernel, then some options are likely different and have been deselected. What I would do is have two terminal windows open, one with make menuconfig from the 2.4 tree (that boots fine) and the other with the 2.6 tree, and compare options.

JM11 · 02-17-2007, 03:02 PM

Ok after some experimenting i realised wat is causing it. I built the ati radeon option as the frame buffer device and this is using my entire screen (1280x800) for the console which is wat i wanted but it's causing this problem of lines. When i built it as a module and only build in the VESA fb it's ok but it boots using 1024x768 which is a bit annoying.

bioe007 · 02-19-2007, 12:21 AM

Quote:

Originally Posted by JM11

make menuconfig
make
make modules_install

something that might help when configuring kernel is to use make xconfig, it explains these options a bit better.

also: make mrproper, make clean and make oldconfig before your make menuconfig (or xconfig) ensures you're set up for remaking your kernel.

make mrproper only once. sorry if you do these already but you didn't mention them.

I have screwed with trying to get FB support and HW acceleration but to my understanding they are mutually exclusive. In order to have a nice FB you have to compile in FB support, but to have HW acceleration you need everything to be modular.

please, anyone correct if I am wrong.

ciotog · 02-19-2007, 06:19 AM

You ought to be able to use initrd with modular framebuffer support, then dump the framebuffer module and load the hw driver before starting X...

duryodhan · 02-19-2007, 10:57 AM

Quote:

In order to have a nice FB you have to compile in FB support, but to have HW acceleration you need everything to be modular.

I am using 2.6.20 with built AGPGART and intel-agp , and HW acceleration is working fine.

My 2c:
JM11, why didn't you use "make bzImage"? thats generally recommended over make... lilo has a real problem with uncompressed images. And instead of "make install" copy over the new bzImage created to /boot/vmcustom and then appropriately change the lilo.conf (add another entry with root=/boot/vmcustom). then do /sbin/lilo twice to be sure

. Thats the easiest method to get a new kernel up and running , without losing your previous one too.

EDIT : don't for make modules_install. All the steps other than this one and copying the image to /boot/ should be preferentially done as non superuser.

JM11 · 02-19-2007, 12:44 PM

I did use make bzImage before hand followed by make modules, and make modules_install. Im currently running the VESA framebuffer rather than the radeonfb so can only get 1024x768 instead of the full 1280x800. I tink its jus LILO that cant handle the widescreen framebuffer resolution. I tink im gna try and install GRUB later on and see if that makes a difference.