Re: Xvesa on FC2 and xcompmgr
Brent Cook <busterbcook-/[email protected]>
| Newsgroups | gmane.comp.freedesktop.xserver |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 31 Mar 2004, Douglas McMorris wrote: > > Now, i have used this server on my Fedora Core 1 system and everything > > just worked fine, but now i have updated to Fedora Core 2-test2 and i > > have some problems. > > > > 1: Xvesa -verbose returns this: > > Mode requested 640x480x4 > > 0x0012: 640x480x4 Planer (4 planes) (no linear framebuffer) > > Static color bpp 4 depth 4 > > Previous modes: VBE 0x4148 BIOS 0x48 > > Enable BIOS mode 0x12 > > Segmentation fault > > I have the same problem. It was fine until i updgraded to FC2-test2 (i > was on test1 before). > > When i run it though gdb it shows that its segfaulting on some assembly > code in vm86.c if that helps anyone. > > from gdb: > > Program received signal SIGSEGV, Segmentation fault. > 0x0804f39a in vm86old (vm=0x87226a0) at vm86.c:684 > 684 asm volatile ( Can you do a backtrace? Just type 'bt' in gdb when the program breaks. I have been looking at the vesa code, and vb86old is too low-level to determine where things really broke; it's probably a function above it that passed a bad parameter, which the backtrace will show. - Brent