Compiling kernel 2.6.26.3 vga=773 doesn't work

verndog · 09-05-2008, 12:57 AM

I am running ubuntu harty. I compiled linux kernel 2.6.26.3 and can't seem to get the vga=773 option to display the graphics text on bootup. Of course I used that on the end of line at menu.lst.

I googled for results. I found something of interest. Someone had very similar issue using Slackware found here

Also my usb flash drives are not detected when I plug them in. Another topic.

the thing I find confusing is I copied the .config file from /boot as instructed.
What's the use of that file if it doesn't include the needed options. I was under the impression that it was the same as my current ubuntu install kernel, which is "2.6.24-21-generic". That works using vga=773.

I have an integrated Intel 865G video. I tried all the frame buffer options using "make xconfig", starting from "General setup > Device Drivers > Graphics support". Nothing seems to work. I'm at my wits end. Anyone else find a solution? Like I said, I have turned on everything I can imagine.

.config section in question:

Code:

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_ALI=m
CONFIG_AGP_ATI=m
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
CONFIG_AGP_SIS=m
CONFIG_AGP_SWORKS=m
CONFIG_AGP_VIA=m
CONFIG_AGP_EFFICEON=m
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
CONFIG_VGASTATE=y
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
CONFIG_FB_ARC=m
CONFIG_FB_ASILIANT=y
CONFIG_FB_IMSTT=y
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
CONFIG_FB_IMAC=y
# CONFIG_FB_N411 is not set
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
CONFIG_FB_S1D13XXX=m
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=y
# CONFIG_FB_I810_GTF is not set
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
CONFIG_FB_INTEL=y
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_CYBLA=m
CONFIG_FB_TRIDENT=m
# CONFIG_FB_TRIDENT_ACCEL is not set
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_LX=m
CONFIG_FB_GEODE_GX=m
CONFIG_FB_GEODE_GX1=m
CONFIG_FB_SM501=m
# CONFIG_FB_VIRTUAL is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_LTV350QV=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_CORGI=m
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_CARILLO_RANCH=m

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

jomen · 09-05-2008, 03:38 AM

Look what I found - the by default very large font size also annoyed me.
Did not test it yet but it looks like what you want.
http://ubuntuforums.org/showpost.php...49&postcount=3
Wouldn't vga=792 look better? (773 - only 8 Bit)

[edit]
This here is related - you could just edit the file:
http://ubuntuforums.org/showpost.php...76&postcount=5
The change from "fixed" to "vga" is doing the trick - as well as the font size setting.

verndog · 09-05-2008, 11:20 AM

jomen, thanks for your reply. I'm not sure but I think the links refer to after the inital boot. I will check out later.

I think my problem lies in the Framebuffer area. I found something in a Gentoo document that looks exactly like my situation. If you go here and read the first two "green" notes, that is what happens to my boot. A blank screen. It states about the the driver has to be built in and NOT as a module.

Then again, I read somewhere else about it being on the 'initrd' side of the equation.

I'll recheck my .config and see if "Enable firmware EDID" is set.

Finally, I haven't been able to get past vga=773. If I try anything more like you suggested, using '791' then the screen goes blank. That's if '773' works at all. I will be happy to just get '793' to work.

jomen · 09-05-2008, 11:55 AM

Everything you need at boot time should not be a module. It could be a little different when you use an initrd like Ubuntu does.
I don't know because I don't use one - I find it more complicated than neccesary.

If you put "vga=ask" instead you should get a list of resolutions your card is capable of.
If you get a blank screen until fully booted (until X starts) it could be that your kernel does not have support for the "Support for the Framebuffer Console Decorations" option in "Graphics support" --> "Console display driver"

CONFIG_FRAMEBUFFER_CONSOLE=m
should be built in.

Also a possible way is: remove the "quiet" and "splash" options from the kernel-line in grub.conf

HTH

verndog · 09-05-2008, 09:32 PM

I discovered something. Outputting 'lsmod' revealed that the generic kernel has almost 30 more modules than the one I built. The ones of importance is these:
fbcon 42912 71
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon

I'm not sure how these are built, through initrd?

jomen · 09-06-2008, 01:12 AM

It is odd but maybe the modules previously there where not deleted - just updated.
Removing the directory /lib/modules/`uname -r` and then re-installing the just built modules should take care of that (make modules_install).
Depends on how you built and installed your kernel. Debian and Ubuntu have tools for that - i.e. create a installable .dpkg from your custom kernel.
You should use these - or go without initrd if you are not sure how to handle it.

verndog · 09-06-2008, 10:10 AM

Quote:

Originally Posted by jomen

It is odd but maybe the modules previously there where not deleted - just updated.
Removing the directory /lib/modules/`uname -r` and then re-installing the just built modules should take care of that (make modules_install).

Yea I just looked at that. For the first few times I compiled it kept complaining about that directory and gave me some info on what to do. From then on, I just deleted it and then compiled. I have check a generic "/lib/modules/..." and there's a big difference in size.

Quote:

Originally Posted by jomen

Depends on how you built and installed your kernel. Debian and Ubuntu have tools for that - i.e. create a installable .dpkg from your custom kernel.
You should use these - or go without initrd if you are not sure how to handle it.

Here's the weird part. I think I'm on to what's not working, just can't seem to get fbcon module to install. I will try again later today, but following this thread I found out what my problem is: http://www.mjmwired.net/kernel/Docum...n/fb/fbcon.txt
If you to there and read the "GOTCHA" that is exactly my issue!

The weird part is I checked those as module install but after building it failed again. Then checking ".config" I noticed that they were still unchecked. I at least now know what needs to be installed.

Regarding going without "initrd" , I don't know how or if I can do that. I'm assuming here it's all in how I compile the kernel. I use this command:
make-kpkg --initrd --revision=2custom kernel_image kernel_headers modules_image
So I guess the "--initrd" needs to be removed, but wouldn't that mess things up?

Also thank you jomen for your interest in my problem. Looks like not much interest in building kernels here. Not just here but I'm finding not a whole lot of web sites with good support. I thinking they are all developers who do this sort of stuff. I find it quite fun, after the first few mishaps. I'm learning a lot.

EDIT:I solved it. I was finally able to get the correct device installed using this from above link:
"Device Drivers->Graphics Support->Support for
22 framebuffer devices->Framebuffer Console Support. Select 'y' to compile
23 support statically, or 'm' for module support. The module will be fbcon"