Tiny Core Base > Micro Core

Using microcore with xorg-xvesa-lite and xbdev

<< < (3/7) > >>

roberts:
You always have the option of using the full Xorg extension.
However this would typically mean that you need an Xorg.conf file.
Therefore it would not be an automatic and is why it is  not currently offered as a .core. type extension.

Note too that for many netbooks with intel video the inclusion of the 915resolution extension will often  automatically setup their non-standard resolutions.

bmarkus:

--- Quote from: roberts on August 05, 2009, 03:23:46 AM ---
However this would typically mean that you need an Xorg.conf file.
Therefore it would not be an automatic and is why it is  not currently offered as a .core. type extension.


--- End quote ---

Why not? For example SLAX by default creates xorg.conf during the startup. It is hidden for the user and works very reliable. Of course you can disable this behavior and keep saved conf if you want.

roberts:
Reallly? When the xorg -configure does not work for my hardware, I typically then do not assume it would work for others without editing. It is one thing when things at least work on my test hardware. Are you saying Xorg configure would auto create the exact resolution that the user wishes?

bmarkus:
My personal experience is that at least on machines I tried it was working. Also on the SLAX forum there are no discussions on this feature as I remember when I was active there. There is one trick, the generated xorg.conf is edited by a script. Do not remember details why, but can dig it out.

Anyhow it is easy. Try SLAX on your machine and see what happenes  ;) This is always good to learn from others....

^thehatsrule^:
slightly OT: iirc, there is the (recent) xorg.confless feature of xorg, but it relies on hal

Navigation

[0] Message Index

[#] Next page

[*] Previous page