...X won't start/hangs
Forum: X and Fluxbox
Topic: ...X won't start/hangs
started by: SaidinUnleashed
Posted by SaidinUnleashed on Sep. 09 2004,21:02
okay, with 0.8.1, i can FINALLY coax DSL to boot, but only with the help of a boot floppy..., and only in "dsl 2 " mode. when i load it normally, or try to start X in rl2, it hangs.
an error message appears JUST before the screen goes blank but it would take superhuman reading speed to read it.
it there anyway to do a "virtual" start of the X server?
what's worse, I broke my 0.7.3 hd install the other night (stupid apt-get) and am stuck using WinblowZzz XP.
-J.P.
SaidinUnleashed
Posted by roberts on Sep. 10 2004,05:42
Try this from runlevel 2. You were using Xvesa if not subsitute Xfbdev# Xvesa -screen 1024x768X16 -dumb
See if you get the big X cursor?
Use Ctrl-Alt-Backspace to get back to text screen. Any error message there?
Posted by coleco on Sep. 12 2004,00:43
okay, im new with linux, i was playen with DSL today and i get the same problem when i try to boot normaley, i dont know what runlevel 2 is, but when i get to the part where it hangs Cntrl-Alt- Backspace dosent work
Posted by SaidinUnleashed on Sep. 12 2004,22:40
Okay, roberts I did what you said and here is the output. Sorry if the formatting is all screwed up, I'm doing this from links in runlevel 2. | Code Sample |
| #Xvesa -screen 1024x768X16 -dumb Interrupt pointer doesn't point at ROM Interrupt pointer doesn't point at ROM apm: overridden by ACPI. Interrupt pointer doesn't point at ROM Interrupt pointer doesn't point at ROM Fatal server error: no screens found Segmentation fault |
Hope you can do something with this.
-J.P.
SaidinUnleashed
Posted by roberts on Sep. 12 2004,22:56
Were you running Xvesa before? Have you tried booting with noapm noacpi ?
How about
boot: fb800x600 2
and then trying at the command prompt
# Xfbdev
Posted by SaidinUnleashed on Sep. 13 2004,00:40
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
Posted by cbagger01 on Sep. 13 2004,01:57
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.
Posted by SaidinUnleashed on Sep. 14 2004,03:27
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
Posted by SaidinUnleashed on Sep. 14 2004,22:48
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
Posted by SaidinUnleashed on Sep. 14 2004,23:11
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