OnTheEdge

Group: Members
Posts: 4
Joined: Dec. 2006 |
 |
Posted: Dec. 13 2006,14:55 |
 |
If I type fb640x480 at boot: then I get this: Could not find kernel image: fb640x48.0 and it puts me back to the boot: prompt.
If I do the "dsl xsetup vga=769" at boot: then it boots, then when xsetup.sh comes up, if I chose fbdev, then when X tries to come up I get: modprobe: modprobe: Can't locate module fb0 XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
If I use xvesa in xsetup.sh instead, then the results are the same as before, the xsri cannot run.
I also tried fb800x600 at the boot: prompt, and the results were EXACTLY the same as when I used "dsl xsetup vga=769", that is vfbdev would give a modprobe error, and xvesa allowed XWindows to come up, but no xsri.
In both cases, I get this during the boot process: You passed an undefined mode number. Press <RETURN> to see video modes available, <SPACE> to continue or wait 30 secs
Any ideas?
|