General TC > Tiny Core Netbooks

800x480 resolution for EEEPC

<< < (3/6) > >>

maro:
The start-up file (i.e. 'usr/local/tce.installed/915resolution') is part of the extension, hence I was suggesting to remove it (via the 'rm ...' command in my suggested steps). In your case it souds like you plan to change it's contents.

If you want to replace '915resolution.tcz' with 'my915resolution.tcz' you will have to remove the (original) '915resolution.tcz' and replace it with your own 'my915resolution.tcz' in your '.../tce/optional' directory. Please note that '...' stands for the mount point where your hard disk or USB drive partition holding your extensions is mounted to. Furthermore you'll have to change the respective entry in '.../tce/onboot.lst'. Alternatively you don't change the file name and just replace the "original" extension file with your "own" one.

bbelden:
I found a fix--at least it appears I have. You were right Maro, since bootlocal gets backgrounded, it's a race to see if bootlocal finishes before Xvesa starts. Since I could reload Xvesa after my machine completed booting and get the proper resolution, I knew this was the case. So I tried putting the 915resolution commands first in my bootlocal file and it worked--boots up with the proper resolution right off the bat. I inserted a comment in my bootlocal file that says: #this command must always run first--so I should be o.k.

Thanks everybody for your help--Tiny Core Rocks!

OldAdamUser2:

--- Quote from: bbelden on May 09, 2010, 09:11:56 AM ---I found a fix--at least it appears I have. You were right Maro, since bootlocal gets backgrounded, it's a race to see if bootlocal finishes before Xvesa starts. Since I could reload Xvesa after my machine completed booting and get the proper resolution, I knew this was the case. So I tried putting the 915resolution commands first in my bootlocal file and it worked--boots up with the proper resolution right off the bat. I inserted a comment in my bootlocal file that says: #this command must always run first--so I should be o.k.

Thanks everybody for your help--Tiny Core Rocks!

--- End quote ---

Fascinating discovery, bbelden! Good  work in finding the proper fix.

mwoodruff:
As a point of reference for anyone else trying to set up an eee 1001p: I found that for the eee 1001p, which uses a GMA3150 graphics adaptor, 915resolution doesn't work.  (It doesn't recognize the GMA3150.)  However, I met success when I loaded these extensions under Tiny Core V3 alpha 3:
graphics-2.6.33.3-tinycore.tcz
Xfbdev.tcz

Without these extensions loaded, I got a perfectly serviceable 800x600 under Xvesa, but with them loaded I get a beautiful native 1024x600.  (I also tried to get Xorg to work with the graphics extension, and it found the intel driver when directed to look for it.  But all I could get from Xorg was a black screen, and Xfbdev works out of the box.)

Juanito:

--- Quote from: mwoodruff on May 21, 2010, 01:55:42 PM ---(I also tried to get Xorg to work with the graphics extension, and it found the intel driver when directed to look for it.  But all I could get from Xorg was a black screen, and Xfbdev works out of the box.)

--- End quote ---

This might be because you need "options i915 modeset=0" in /etc/modprobe.conf before loading the graphics-2.6.33.3-tinycore extension

Navigation

[0] Message Index

[#] Next page

[*] Previous page