Summary: | [vesafb-tng] gentoo-sources-2.6.21 - vesafb BUG, returned from vm86 with ffffffff (EIP: 0xc0fb2) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dekel Amrani <dekela> |
Component: | [OLD] Core system | Assignee: | Michal Januszewski (RETIRED) <spock> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | duaneg, kernel, vincent.poinot |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dekel Amrani
2007-05-18 10:45:46 UTC
Any news regarding this bug? Any news? Is anybody looking into this? 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. It's probably irrelevant here, but you should use 'mtrr:3' and not 'mtrr' with vesafb(-tng). 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. 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. |