Tiny Core Base > Alpha Releases
Tiny Core 3.0 Alpha 1 Testing
yoshi314:
one thing that might be important - ati driver now requires a small piece of firmware for accelerated operation.
one for KMS (all cards) , second for Xorg (some cards).
in case of my x1300 card, i need /lib/firmware/radeon/R520_cp.bin or KMS might fail to start.
Juanito:
I foresee all kinds of fun coming with Xorg-7.5 testing :)
bmarkus:
--- Quote from: curaga on May 10, 2010, 06:46:51 AM ---Possible speed gains and size losses, nothing guaranteed though.
--- End quote ---
OK, I will make some tries and see result :)
jur:
--- Quote from: curaga on May 10, 2010, 05:38:41 AM ---Short: Intel graphics users wanting Xorg, you'll need to change the default to UMS mode for Xorg 7.4. 7.5 will support KMS.
Long:
What you're seeing is Intel's new graphics stack.
They only support KMS now (in the Xorg driver, the kernel driver still has the UMS mode for backwards compatibility); if you wish to use UMS, add "options i915 modeset=0" to /etc/modprobe.conf before loading the extension/module.
As you've seen, the KMS stack conflicts with both the vesa framebuffer and the vesa driver (both tinyX and Xorg), because it sets the resolution itself. It gives less flicker, and the optimal resolution from the start (full-res console).
The module in KMS mode should be loaded in pure text mode; inside X or with a framebuffer it's likely to crash and burn.
So far Intel is the only one going this far; radeon and nouveau also support KMS, but theirs defaults off.
The intel driver in Xorg 7.4 doesn't support KMS IIRC, so to run with it turn modesetting off.
--- End quote ---
Thanks, I was able to make it work. Here are the steps I followed to get it to boot up into Xorg:
0. Xorg-7.4 and grpahics-2.6.33.3 must NOT be in the onboot list.
1. I added "options i915 modeset=0" to /etc/modprobe.conf and added it to filetool.
2. I added tce-load instructions for graphics-2.6.33.3-tinycore and Xorg-7.4 to .profile before the final startx statement.
That was it. This procedure was necessary as the extensions must be loaded after the modprobe.conf file gets restored. I don't know how to do it otherwise - is there a better, more streamlined method?
bmarkus:
--- Quote from: curaga on May 10, 2010, 06:46:51 AM ---Possible speed gains and size losses, nothing guaranteed though.
--- End quote ---
Using the same build script, mc.tcz is 586k on 3.0 while 606k on 2.10
Speed? No idea :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version