|Summary:||Using Xvesa gives Interrupt pointer doesn't point at ROM|
|Product:||xorg||Reporter:||Matthew Lyszczek <mlyszczek>|
|Component:||Server/DDX/Xephyr||Assignee:||Keith Packard <keithp>|
|Status:||CLOSED WONTFIX||QA Contact:|
|i915 platform:||i915 features:|
Description Matthew Lyszczek 2003-12-14 18:41:23 UTC
Hi, I compiled Xserver using ebuilds for Gentoo. However when I go to start this using Xvesa, I get the following: Interrupt pointer doesn't point at ROM Interrupt pointer doesn't point at ROM Interrupt pointer doesn't point at ROM Interrupt pointer doesn't point at ROM Fatal server error: no screens found Segmentation Fault I'm using an nVidia GeForce 5600 Ultra and I've update to the latest CVS on occasion and still nothing.
Comment 1 Peter Lietz 2004-04-07 15:21:07 UTC
I have the same problem on debian sid. Moreover, "Xvesa -listmodes" will only offer video modes with a maximum resolution of 640x480. My video card is Nvidia GeForce Ti4200 based. Compilation, however, went flawlessly via the xserver-inst.sh script. BTW, I know this is not the right spot to bring this up, but are there any specific kernel settings or modules (dri, agpgart,...) necessary in order to run xserver?
Comment 2 Juliusz Chroboczek 2006-10-30 13:55:42 UTC
> Interrupt pointer doesn't point at ROM This usually means that something modified the real-mode interrupt pointers before booting Linux. Are you cold-booting, or warm-booting after running a different OS? It can also mean that your BIOS sets up things in a way that doesn't obey the VESA specs (unlikely), or that something you do under Linux remaps the real-mode interrupt vectors, but I cannot imagine what that could be. > Moreover, "Xvesa -listmodes" will only offer video modes with a maximum > resolution of 640x480. Ah-ha -- this means that your video card's BIOS doesn't support VESA. If so, I'm afraid you're condemned to using a kernel-mode framebuffer driver with Xfbdev. Juliusz
Comment 3 Adam Jackson 2009-04-14 07:17:51 UTC
The old kdrive tree is dead. As far as we can tell, this bug no longer applies to the current Xorg server tree. If it does, please reopen this bug and change the product to 'xorg' and the component to 'server/general'.