Description of Problem: I've updated a system runing RHL8 to beta1. The machine has a GeForce4 card and was using the vesa driver. After the update the XF86Config file still litst the vesa driver as being used but X does not show any sign of life. Version-Release number of selected component (if applicable): XFree86-4.2.99.2-0.20021110.3 How Reproducible: Always Steps to Reproduce: 1. Start X on system updated from RHL8 2. 3. Actual Results: (EE) VESA(0): vm86() syscall generated signal 4. (EE) Scnree(s) found, but non have a usable configuration. Expected Results: X starts up and shows nice pictures. Additional Information: This is a P4 UP HT machine running the SMP kernel (and therefore has two CPUs)
Created attachment 85864 [details] Config file after the update
Maybe I should add that this is a GeForce4 card.
Just for other people that might find this bug report as well... For CVS XFree86, you should configure the card to use the "nv" driver, instead of the "vesa" driver. XFree86 CVS has native GeForce 4 support now. The vesa driver probably should still work also though, so I'll keep this open to investigate with some Nvidia hardware.
I'm wondering if kernel changes may be responsible for this perhaps? Would NPTL or anything else potentially get in the way of vm86?
NPTL might well have an impact on what is in the segment registers, especially if the XFree86 int code for VESA is not NPTL aware. May need some Xserver hacking
The same machines run the final RHL9 and RC test2. I'm closing the bug. Must have been temporary insanity on the side of the nv driver.