X and Fluxbox :: ...X won't start/hangs

I have tried all of that. When trying to use Xvesa, it has the same problem. With Xfbdev, I get this.

Code Sample

Init error
. . .
no screens found

Also, I remembered that in the latest versions of both XF86 and X.org, I have to crawl through the config file and manually set the display driver to "radeon". The vesa driver doesn't work on either of them.

My guess is that the Xvesa that is in 0.8.x is derived from the vesa driver from a version of X that doesn't work with Radeons.

I guess it sucks to be me.

I wonder if coleco has a radeon as well?

-J.P.
SaidinUnleeashed

I am using the Xvesa server and DSL version 0.8.1.1 with my Radeon 9600 XT AGP card and it works fine for me.

I doubt that the problem is with supported video cards because ATI usually provides good VESA support for their products.

I could be wrong, but that's just my opinion.

Hmm, the card on my desktop is a 9600 pro, but on an older comp (with a 7000) i have to manually set it to radeon in X as well.

haven't tried it with DSL yet (it's a "new" frankenstein)

i will hav to play around with this some more.

-J.P.
SaidinUnleashed

Okay, did some googlng and found a few more things to try, and here is the output.

Code Sample

# Xvesa -verbose -videoTest
Interrupt pointer doesn't point at ROM
Interrupt pointer doesn't point at ROM
Mode requested 640x480x4
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
Static color 4 depth 4
Mode selected 640x480x4
apm: overridden by ACPI.
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: No such device
insmod: Hint insmod errors can be caused by incorrect module parameters, including invalid IO od IRQ parameters.
Youmay find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.26/kernel/arch/i386/kernel/apm.o: insmod char-major-10-134 failed
Interrupt pointer doesn't point at ROM
Previous modes: VBE 0xffffffff BIOS 0x54
Enable BIOS mode 0x12
Interrupt pointer doesn't point at ROM

Fatal server error:
no screens found
Segmentation fault

notice that it says that apm has been overridden by ACPI?

well, i booted with noacpi.

this is annoying...

-J.P.
SaidinUnleashed

remembered a little trick.

failsafe

worked. now i get to do "expert" untill i find the offending module.

kind of feel like an idiot...

-J.P.
SaidinUnleashed

Next Page...
original here.