Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 178985 - [vesafb-tng] gentoo-sources-2.6.21 - vesafb BUG, returned from vm86 with ffffffff (EIP: 0xc0fb2)
Summary: [vesafb-tng] gentoo-sources-2.6.21 - vesafb BUG, returned from vm86 with ffff...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Michal Januszewski (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-18 10:45 UTC by Dekel Amrani
Modified: 2007-10-11 19:54 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dekel Amrani 2007-05-18 10:45:46 UTC
Kernel:2.6.21-gentoo

Kernel boot arguments:kernel /boot/kernel-2.6.21-gentoo root=/dev/sdb4 root=/dev/sdb4 splash=verbose,fadein,theme:livecd-2007.0 video=vesafb:ywrap,mtrr,1280x1024-16@60 fbcon=scrollback:128K quiet

Error:
vesafb: unrecognized option mtrr
vesafb: BUG, returned from vm86 with ffffffff (EIP: 0xc0fb2)
vesafb: warning, copying modelist from somewhere in RAM!
vesafb: Sorry, pre-VBE 2.0 cards are not supported.
vesafb: vbe_init failed
vesafb: probe of vesafb.0 failed with error -22



Reproducible: Always

Steps to Reproduce:
lspci:
01:00.0 VGA compatible controller: nVidia Corporation G71 [GeForce 7900 GT/GTO] (rev a1)

monster dekela # cat /usr/src/linux/.config | grep FB
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_FB=y
# CONFIG_FB_DDC is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT 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 is not set
CONFIG_FB_VESA_TNG=y
CONFIG_FB_VESA_DEFAULT_MODE="1280x1024@60"
# CONFIG_FB_IMAC is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 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_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_SPLASH=y
monster dekela #
Comment 1 Dekel Amrani 2007-05-25 14:10:33 UTC
Any news regarding this bug?
Comment 2 Dekel Amrani 2007-06-05 20:00:20 UTC
Any news?
Is anybody looking into this?
Comment 3 Duane Griffin 2007-06-05 22:43:48 UTC
Sorry for the delay, let's see if we can figure out what is going on.

First, has it ever worked for you with other kernels, kernel parameters or hardware?

Next, please reboot without the "quiet" kernel param and attach your dmesg.

Finally, could you try using the standard FB_VESA framebuffer driver instead of FB_VESA_TNG to see if it works. Also, please attach your dmesg after booting with it.
Comment 4 Michal Januszewski (RETIRED) gentoo-dev 2007-06-06 18:53:22 UTC
It's probably irrelevant here, but you should use 'mtrr:3' and not 'mtrr' with vesafb(-tng).
Comment 5 Vincent Poinot 2007-10-07 18:14:04 UTC
Just wanted to confirm the original report: I have exactly the same result, in pretty much the same circunstances:
- kernel 2.6.22
- nvidia Quadro FX Go 1400,
- regarding kernel parameters, I do use mtrr:3, no fbcon, no quiet option,
- I ask for 1400x1050-16@60 because I *know* this was working before I upgraded to 2.6.22 (I had 2.6.20, with fbsplash running fine, removed Gentoo and reinstalled it some time later with 2.6.22 and exactly the same grub.conf, and now I get exactly the same error messages as reported).

So ok, I will try vesa (instead of vesa-tng), but it used to work with vesa-tng.
Comment 6 Michal Januszewski (RETIRED) gentoo-dev 2007-10-11 19:54:08 UTC
I'm closing this bug as WONTFIX since we're dropping support for vesafb-tng. vesafb-tng has been replaced by uvesafb in gentoo-sources-2.6.23. uvesafb provides the same functionality, but is completely redesigned and hopefully will prove to be free of any bugs that might have been present in vesafb-tng.

If you encounter a similar problem with uvesafb, please open a new bug.