Search Members Help

» Welcome Guest
[ Log In :: Register ]

Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic
Pages: (9) </ 1 2 [3] 4 5 6 7 8 ... >/

[ Track this topic :: Email this topic :: Print this topic ]

reply to topic new topic new poll
Topic: All the colors are off!, Incorrect color rendering with Xvesa< Next Oldest | Next Newest >
roberts Offline





Group: Members
Posts: 4983
Joined: Oct. 2003
Posted: July 23 2004,00:24 QUOTE

[QUOTE}modprobe: Can't locate module fb0[/QUOTE]

This usually indicates that the framebuffer was not specified at the boot prompt .  How did you boot?  Should be:

boot: fb800x600  and not   boot: dsl fb800x600
Back to top
Profile PM WEB 
RobF
Unregistered






Posted: July 23 2004,01:57 QUOTE

The list of boot time options accessible with F2 shows that the framebuffer options are to be entered without dsl preceding them.  So that's what I've done, i.e. boot: fbxxxxxxx, where xxxxxxx stands for 800x600, etc.

I would have thought that that would bypass any additional config screens; yet I still have to navigate through the "DSL X Setup" box that asks you to choose between xvesa and xfbdev, as though that fbxxxxxxx option specified at the boot prompt somehow hasn't taken.

Anyway, in whatever way xfbdev is chosen, that option always crashes with the errors that I posted above.

With xvesa I get to the dsl desktop but the colors are all off except for 640x480.  When I kill the Xserver (with CTRL-ALT-Backspace) in one of the modes that renders colors incorrectly, I get to the text prompt dsl@tty1[dsl]$.  The lines preceding that prompt show me any error messages the kernel put out just before it switched on the X server.

One error I commonly find there is:

IMLIB ERROR: Cannot find palette.  A palette is required for this mode.

Another error message I sometimes see there is an entire screen full of messages saying:

rxvt: can't load color "........"

where ....... stands for one of many different colors, e.g. Blue3, Red3, Green3, etc.
Back to top
cbagger01 Offline





Group: Members
Posts: 4264
Joined: Oct. 2003
Posted: July 23 2004,02:23 QUOTE

Rob,

I think that you are confusing the 16 bit color depth with the 16 COLORS color depth (aka 4 bit color).

The Intel guide quote mentioned 16colors mode, not 16 bit color.

Try booting your computer with a 4 bit color mode like 800x600x4bit

You should then be able to use the xfbdev driver.

Who knows, maybe even the xvesa will work at 800x600 in 4bit color mode. I dunno.  Search the forums for information about custom framebuffer resolutions.
They usually can be created by typing in something like 'dsl vga=0x302' or something like that.

Good Luck.
Back to top
Profile PM 
RobF Offline





Group: Members
Posts: 22
Joined: July 2004
Posted: July 23 2004,05:33 QUOTE

Whenever I referred to 16 in connection with color depth, I was referring to 16 bit color depth rather than 16 colors.  I hardly tested the 4 bit mode (i.e. 16 colors) as I expected a pretty horrible outcome.  When I run Mandrakelinux 10.0 or Xandros 2.0 or Libranet 2.8.1, I'm using 1024x768x16, i.e. >10,000 colors.

Anyway, re 800x600 at 4 bit with xfbdev.  I have to repeat: when I use boot: fb800x600 (that's all, on the boot command line you cannot specify color depth), I still wind up in the "DSL X Setup" box which asks me to choose xvesa or xfbdev.  When I choose xfbdev, the next box asks me: Do you have a USB mouse -> Yes, I click on Yes and bang, rather than going on to ask "what color depth", as it does when I choose Xvesa, the config program crashes and dumps me to the DSL command line, I never see an X Windows desktop.  NO POSSIBLE SETUP OF XFBDEV HAS EVER GOTTEN ME TO AN X WINDOW.

Re 800x600 at 4 bit with xvesa.  I tried that, and I get to the DSL Desktop with the DSL manual in Dillo - and with Tux with blue feet!  So it doesn't work.  When I kill the X server, I get dropped to the dsl text prompt, and I can see the last error messages that the kernel put out before it started X.  In this case they were:

Failed to load groupfile
BScreen : : BScreen: managing screen 0 using visual 0x21, depth 8

I also tried various settings of vga=xxxxxx and dsl vga=xxxxxxx at the boot prompt, using a list of a dozen different modes that someone had compiled for DSL.  None of that worked.  I think DSL simply ignored that I had already specified a video mode on the boot screen and dragged me through the whole setup sequence with the DSL X Setup boxes which essentially does the same thing, i.e. specify a video mode.  I've spent countless hours now fiddling with video setup for DSL and trying to find out what's wrong; never had that much trouble before with video setup.  I think there is something fundamentally flawed about those TinyX servers (i.e. xvesa and xfbdev) that DSL uses.

Maybe the DSL developers should do something to fix them to support more hardware or dump them altogether.  It seems to be hard to find out anything about them - their website seems to be migrating, there seems to be no support for them, and nobody even seems to know what versions are used in DSL 0.7.2 and how old they are.

The Intel Advanced Graphics Chipset that's integrated in my motherboard works without a flaw with 5 different big Linux distros that I have installed on my machine and that use X86Free v. 11.  With them I can play Tuxracer with accelerated 3D graphics in full color and at high speed.  I'm not willing to disable this perfectly adequate onboard graphics support and buy a separate video card just to run DSL.

I thought that I could perhaps replace TinyX with X86Free and remaster the CD.  I tried that by following the advice in the parallel thread "How to replace xvesa with x86free".  Didn't work.  Tried "apt-get install x-window-system" and "apt-get install xserver-xfree" on the command line, as both normal user and as root.  Error: "no command apt-get".  Supposedly apt is installed with DSL.  What's wrong?

I had wanted to use DSL to impress those of my friends who are captive to MS Windows with how much can be done with Linux even on a tiny 50 MB footprint on a business card CD.  I don't think they'd be impressed with blue-faced people.

Robert
Back to top
Profile PM 
cbagger01 Offline





Group: Members
Posts: 4264
Joined: Oct. 2003
Posted: July 23 2004,12:16 QUOTE

Robert,

The xsetup script will always run when you boot up from livecd when you specify the framebuffer values.  The script is used to select the x server of choice and to specify your mouse configuration, so it needs to be run.  It is possible that there are some users that wish to run a certain size framebuffer while in "text" mode and still run Xwindows from the xvesa server.

The default DSL install must use the tinyx servers because you cannot do a full install of xfree86 and still fit everything on a 50MB business card size CD-R disk.

If you wish to install programs with apt-get, you first need to select "Enable Apt" from the menu. After the dpkg / apt system is restored your apt command should start working.

Unfortunately, due to space considerations on DSL it appears unlikely that you will be able to impress your friends with it on an i810 based computer until/unless Intel comes up with a firmware/BIOS change to allow their hardware to work with the INDUSTRY STANDARD vesa functions.  It is also possible that either the "TinyX" folks could rewrite their code to support the uniqueness of the i810 server, OR some kernel writer could add support for a specialized i810 framebuffer which would then work with the xfbdev server.  I wouldn't hold my breath waiting for any of these however.
Back to top
Profile PM 
43 replies since July 17 2004,06:05 < Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (9) </ 1 2 [3] 4 5 6 7 8 ... >/
reply to topic new topic new poll
Quick Reply: All the colors are off!

Do you wish to enable your signature for this post?
Do you wish to enable emoticons for this post?
Track this topic
View All Emoticons
View iB Code