LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   kernel 2.6.3 => dark screen at boot (http://www.linuxquestions.org/questions/slackware-14/kernel-2-6-3-%3D-dark-screen-at-boot-152535/)

deb75 03-02-2004 06:35 AM

kernel 2.6.3 => dark screen at boot
 
Hello,

I currently run the slackware 9.1 with its original kernel 2.4.22
I wanted to upgrade to 2.6.3

so I downloaded it, and compiled it with nearly same config as the 2.4.22
but when I booted the 2.6.3 ... it gave a dark screen without anything ( I am in text mode )

however the hard disk led went on blinking, which let me think that the kernel was accessing correctly to the HDD,

I did not changed anything in any files on the slackware9.1 between 2.4.22 and 2.6.3, the
2.4.22 still boots well,

I noticed in the 2.6.3 config menu ( make menuconfig ) that I did not see the 'support for virtual terminal' options whereas it is clearly written in that of 2.4.22

but when I looked in the .config (2.6.3) generated after 'make menuconfig' I saw :
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

so I wonder where the pb comes from ?

could someone send me one config file for 2.6 kernel, which is sure to work ?
my hardware config is : MSI K7N2 delta-l (nvidia-nforce2)
IDE HDD
IDE-ATAPI CDROM
graphic card : asus nvidia geforce4 MMX440

thanks for your help

AxeZ 03-02-2004 07:25 AM

Just leave out any framebuffer devices in the kernel config and use just simple VESA VGA

deb75 03-02-2004 07:33 AM

thanks for answering axeZ

although I did not know exactly what is framebuffer for , I compiled it as a module, I will
check this

what is the difference between framebuffer and vesa vga ?

AxeZ 03-02-2004 07:46 AM

Quote:

Originally posted by deb75
thanks for answering axeZ

although I did not know exactly what is framebuffer for , I compiled it as a module, I will
check this

what is the difference between framebuffer and vesa vga ?


Actually VESA VGA is frambuffer and is generic, just leave out any other card they mention in kernel config.

A framebuffer device is an abstraction for the graphic hardware. It represents the frame buffer of some video hardware, and allows application software to access the graphic hardware through a well-defined interface, so that the software doesn't need to know anything about the low-level interface stuff [Taken from Geert Uytterhoeven's framebuffer.txt in the linux kernel sources]

I suggest reading

http://www.tldp.org/HOWTO/Framebuffer-HOWTO.html

motub 03-02-2004 08:27 AM

Well, I had this problem too when I compiled and installed 2.6.3, and the easiest way to get the boot messages until I figured out how to get the framebuffer working (which it now does), was to re-comment vga=### in /etc/lilo.conf and uncomment vga=normal.

You get the giant vga text again and not the nice neat framebuffer text, but at least you can see it.

I honestly don't know how I fixed it, though-- I recompiled the kernel a couple of times, but as far as I could see, I had already set the framebuffer console and the VESA and VGA consoles, so I didn't change those, but I did have to remove DRI and modularize AGPGART-- the whole reason I was recompiling the kernel again anyway was to prepare it for the installation of the proprietary ATI drivers for my videocard-- and at some point during the recompiling, checking the how-tos, recompiling again because I did something wrong, and compiling and installing the driver modules, framebuffer boot suddenly worked (with Tux at the top, since I had renabled the boot logo at some point... in fact I think it was Tux's sudden reappearance that tipped me off that I should try the fb again).

So I'm sorry that my best advice is to just fiddle with it until it works, or just use vga=normal and don't worry about it, but... there you go.

Hope this helps :) .


All times are GMT -5. The time now is 01:33 AM.