| View previous topic :: View next topic |
| Author |
Message |
coroner21
n00b
Joined: 27 Jul 2005
Posts: 7
|
 Posted: Thu Oct 20, 2005 11:10 am Post subject: vesafb is not working anymore since 2.6.13 |
 |
|
Since kernelversion 2.6.13 vesafb is not working anymore. I got an amd64 with nvidia 6600. The relevant parts of my .config:
| Code: |
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_FB_VESA_STD=y
# CONFIG_FB_VESA_TNG is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
CONFIG_FB_SPLASH=y
|
With a 2.6.12 kernel vesafb worked pretty good and fbsplash was looking nice. Now, on boot, all I get is the message, that I've specified an invalid mode number.
Grub kernel line:
| Code: |
kernel /boot/kernel-2.6.13-gentoo-r3 root=/dev/hda2 ro elevator=cfq video=vesafb:ywrap vga=0x31B noexec=on quiet
|
|
|
| Back to top |
|
 |
abester
Tux's lil' helper
Joined: 09 May 2005
Posts: 93
|
| Posted: Thu Oct 20, 2005 12:02 pm Post subject: |
|
|
| Hi, I have the same .config regarding FB section, except for the CONFIG_FB_VGA16 which I have compiled in. Also double check Tile Blitting is off, and that vesa driver type is set to vesafb. Sometimes my splash doesn't work when I passed a wrong video mode, try setting it to 0x317 and experimenting upwards from there. |
|
| Back to top |
|
|
deepwave
Tux's lil' helper
Joined: 18 Jan 2004
Posts: 122
Location: ONS Insomniac
|
| Posted: Thu Oct 20, 2005 12:11 pm Post subject: |
|
|
Why not try using the vesafb-tng framebuffer or the one specifically for ATI cards?
_________________
Current open source project: justCheckers, a cross-platform checkers suite. |
|
| Back to top |
|
|
coroner21
n00b
Joined: 27 Jul 2005
Posts: 7
|
| Posted: Thu Oct 20, 2005 12:53 pm Post subject: |
|
|
To deepwave: Since I have a nvidia card, I cannot use the ATI fb-driver. And vesafb-tng is not available on amd64.
abester: I compiled my kernel with CONFIG_FB_VGA16=yes and I will set another mode. I'll report back... |
|
| Back to top |
|
|
coroner21
n00b
Joined: 27 Jul 2005
Posts: 7
|
| Posted: Fri Oct 21, 2005 7:46 am Post subject: |
|
|
| Well, this seems odd... While vesafb initializes with vga=0x318 it doesn't work anymore when passing a higher mode on kernel commandline. So passing vga=0x31B (for 1280x1024-32) is only generating a message about me passing a wrong mode number. I don't think, that this is the right behaviour since this was working fine on any 2.6.12 kernel and it is specified in the documentation as the right mode number for 1280x1024-32. Anybody got this mode working with vesafb? Anybody knows about codechanges that led to this? I would definitely love to have vesafb working at 1280x1024-32 again... |
|
| Back to top |
|
|
coroner21
n00b
Joined: 27 Jul 2005
Posts: 7
|
| Posted: Fri Oct 21, 2005 12:44 pm Post subject: |
|
|
| I noticed another really annoying thing. While it works to have vesafb with vga=0x318 the console is totally unusable after X has been started. If I switch to a text-console, I just get some garbage on the screen. While this may be related to nvidia-driver updates, I didn't notice such a problem with 2.6.12 and running vesafb at 0x31B. |
|
| Back to top |
|
|
|
Kernel & Hardware
