Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: ECHOSIDE on October 05, 2013, 11:00:15 AM
-
The native resolution for my monitor is 1920x1080x24 60 Hz. When using Xvesa, I see that the highest resolution option available is 1024x768x24. This resolution is far below my monitor's capability and it is the wrong aspect ratio. How can I get Tiny Core to display at 1920x1080x24 60 Hz?
Thank you
-
Use Xorg-7.7 instead of Xvesa
-
Thank you for your response, Juanito. I installed Xorg, but when trying to switch over, I get the error:
Fatal server error:
(EE) Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
I tried dropping to console with Ctrl+Alt+F1 but received the same error. I also briefly perused http://wiki.x.org but did not find an answer. Can anyone provide assistance for switching to Xorg?
Thank you
-
Use the apps browser to remove xvesa and install Xorg then reboot
Sent from my iPad using Tapatalk HD
-
Sounds like your video card's VESA support lacks what you want. I can confirm I've used 5.0 with Xvesa at 1920x1080
-
genec, That's interesting!!!
Almost all my monitors start at 1920x1080 which so far have needed proprietary drivers to achieve
I must try, there is a thread around here somewhere with more info..
-
Heck I never knew I could run 1920x1200 on my notebook using Xvesa.tcz before, it works !!
-
Xvesa -listmodes
;)
-
Thanks, I've been looking for that
tc@box:~$ Xvesa -listmodes
VBE version 3.0 (NVIDIA)
DAC is fixed, controller is VGA compatible, RAMDAC causes snow
Total memory: 14336 kilobytes
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor
0x0100: 640x400x8 PseudoColor
0x0101: 640x480x8 PseudoColor
0x0102: 800x600x4 Planar (4 planes) (no linear framebuffer)
0x0103: 800x600x8 PseudoColor
0x0104: 1024x768x4 Planar (4 planes) (no linear framebuffer)
0x0105: 1024x768x8 PseudoColor
0x0106: 1280x1024x4 Planar (4 planes) (no linear framebuffer)
0x0107: 1280x1024x8 PseudoColor
0x010E: 320x200x16 TrueColor [5:6:5:0]
0x010F: 320x200x24 TrueColor [8:8:8:8]
0x0111: 640x480x16 TrueColor [5:6:5:0]
0x0112: 640x480x24 TrueColor [8:8:8:8]
0x0114: 800x600x16 TrueColor [5:6:5:0]
0x0115: 800x600x24 TrueColor [8:8:8:8]
0x0117: 1024x768x16 TrueColor [5:6:5:0]
0x0118: 1024x768x24 TrueColor [8:8:8:8]
0x011A: 1280x1024x16 TrueColor [5:6:5:0]
0x011B: 1280x1024x24 TrueColor [8:8:8:8]
0x0130: 320x200x8 PseudoColor
0x0131: 320x400x8 PseudoColor
0x0132: 320x400x16 TrueColor [5:6:5:0]
0x0133: 320x400x24 TrueColor [8:8:8:8]
0x0134: 320x240x8 PseudoColor
0x0135: 320x240x16 TrueColor [5:6:5:0]
0x0136: 320x240x24 TrueColor [8:8:8:8]
0x013D: 640x400x16 TrueColor [5:6:5:0]
0x013E: 640x400x24 TrueColor [8:8:8:8]
0x0145: 1600x1200x8 PseudoColor
0x0146: 1600x1200x16 TrueColor [5:6:5:0]
0x014A: 1600x1200x24 TrueColor [8:8:8:8]
0x0160: 1280x800x8 PseudoColor
0x0161: 1280x800x24 TrueColor [8:8:8:8]
0x0162: 768x480x8 PseudoColor
0x017B: 1280x720x24 TrueColor [8:8:8:8]
0x017C: 1920x1200x8 PseudoColor
0x017D: 1920x1200x24 TrueColor [8:8:8:8]
tc@box:~$
-
Xvesa -help
;)
-
Dell Latitude E6540 (AMD Radeon HD8790M + Intel) (mode 0x017F is choice #10 in xsetup.sh)
VBE version 3.0 (Intel(R) HSW Mobile/Desktop Graphics Chipset Accelerated VGA BIOS)
DAC is fixed, controller is VGA compatible, RAMDAC causes snow
Total memory: 32704 kilobytes
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor
0x0107: 1280x1024x8 PseudoColor
0x011A: 1280x1024x16 TrueColor [5:6:5:0]
0x011B: 1280x1024x24 TrueColor [8:8:8:8]
0x0105: 1024x768x8 PseudoColor
0x0117: 1024x768x16 TrueColor [5:6:5:0]
0x0118: 1024x768x24 TrueColor [8:8:8:8]
0x0112: 640x480x24 TrueColor [8:8:8:8]
0x0114: 800x600x16 TrueColor [5:6:5:0]
0x0115: 800x600x24 TrueColor [8:8:8:8]
0x0101: 640x480x8 PseudoColor
0x0103: 800x600x8 PseudoColor
0x0111: 640x480x16 TrueColor [5:6:5:0]
0x017D: 1920x1080x8 PseudoColor
0x017E: 1920x1080x16 TrueColor [5:6:5:0]
0x017F: 1920x1080x24 TrueColor [8:8:8:8]
-
I reverted to Xvesa based on the information that it is capable of displaying 1920x1080. I may switch to Xorg again in the future, but I am fond of Xvesa's lightweight and intuitive design. Xvesa -listmodes produces
VBE version 3.0 (NVIDIA)
DAC is fixed, controller is VGA compatible, RAMDAC causes snow
Total memory: 131072 kilobytes
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor
0x0100: 640x400x8 PseudoColor
0x0101: 640x480x8 PseudoColor
0x0102: 800x600x4 Planar (4 planes) (no linear framebuffer)
0x0103: 800x600x8 PseudoColor
0x0104: 1024x768x4 Planar (4 planes) (no linear framebuffer)
0x0105: 1024x768x8 PseudoColor
0x010E: 320x200x16 TrueColor [5:6:5:0]
0x010F: 320x200x24 TrueColor [8:8:8:8]
0x0111: 640x480x16 TrueColor [5:6:5:0]
0x0112: 640x480x24 TrueColor [8:8:8:8]
0x0114: 800x600x16 TrueColor [5:6:5:0]
0x0115: 800x600x24 TrueColor [8:8:8:8]
0x0117: 1024x768x16 TrueColor [5:6:5:0]
0x0118: 1024x768x24 TrueColor [8:8:8:8]
0x0130: 320x200x8 PseudoColor
0x0131: 320x400x8 PseudoColor
0x0132: 320x400x16 TrueColor [5:6:5:0]
0x0133: 320x400x24 TrueColor [8:8:8:8]
0x0134: 320x240x8 PseudoColor
0x0135: 320x240x16 TrueColor [5:6:5:0]
0x0136: 320x240x24 TrueColor [8:8:8:8]
0x013D: 640x400x16 TrueColor [5:6:5:0]
0x013E: 640x400x24 TrueColor [8:8:8:8]
As you can see, 1920x1080 is not an option yet. Is this a driver issue? If so, how can I find out which driver I need? How do I obtain it and install it?
Thank you
-
As far as I know, Xvesa will only display the resolutions from -listmodes - if your desired resolution is not in the list, I believe you'll need Xorg.
-
Hi ECHOSIDE
It's a long shot, but you could try something like:
Xvesa -mode 017F -force
-
I rerverted to Xvesa based on the information that it is capable of displaying 1920x1080. I may switch to Xorg again in the future, but I am fond of Xvesa's lightweight and intuitive design. Xvesa -listmodes produces
As you can see, 1920x1080 is not an option yet. Is this a driver issue? If so, how can I find out which driver I need? How do I obtain it and install it?
Xvesa can do that if and only if the video card itself bothers to have an appropriate VESA mode. There is NO driver to help this (that's where Xorg comes in). You might find an update to the firmware in the video card may help but don't count on it. A while back, I had a machine that pretty much never played nicely with VESA yet systems before and after it in its make/family would. If it's an onboard card, check for BIOS updates.
Using the -force option may work but it's not very reliable. In fact, it may take that mode number and do something unexpected with it (like another screensize) but it could be worth a shot.
-
I have never posted a topic in any forum that has received so many helpful and thoughtful responses. All of you seem informed and willing to help a newbie. The Tiny Core community seems pretty cool.
I'm going to go for Xorg now. Hopefully that will get me to my native resolution without too much more effort.
-
By reading http://wiki.tinycorelinux.net/wiki:using_xorg_over_xvesa (http://wiki.tinycorelinux.net/wiki:using_xorg_over_xvesa), I learned that the way to get out of "confless" mode was to create /etc/X11/xorg.conf. I took ownership of the directory and created the file to spec, but when I reboot, the directory /X11/ and file are gone. I must be missing something fundamental about the filesystem or the implementation of persistence.
I feel like I'm at a wall. Does anyone have any advice on how to proceed?
Thank you.
-
add etc/X11/xorg.conf to /opt/filetool.lst and use the cpanel gui to make a backup
-
Ok, that worked. I've also got a clearer understanding of how persistence works in Tiny Core. Learning commands and syntax for Xorg.conf has been time consuming. Do I need drivers for my video card "[GeForce 7150M / nForce 630M] (rev a2)"? If so, should I get the drivers from Nvidia's website or from somewhere else?
-
There are 2 nvidia xorg drivers in the repo.
xf86-video.nv.tcz
and
xf86-video-nouveau.tcz
Try each one separately.
It looks like the nouveau driver supports your video card.
-
I have an nvidia (geforce 210) card and can only use Xvesa or proprietary nvidia drivers if using Xorg.
Anything else is unusable slow on my system.
On TC 4.7.7 I've created an nvidia drivers extension using scripts by Rich:
http://forum.tinycorelinux.net/index.php/topic,12965.msg71304.html#msg71304
However, the driver did not work correctly when compiled under TC 5.x . I think some dependencies, which I might have just copied from TC 4.x, need to get rebuild for 5.x .
-
Just get the source for the latest driver from nvidia's web site and compile that against full Linux sources
Instructions are included, use those
And no deps needed
-
Thanks I'll try.
Maybe Rich's scripts are 'outdated'.
-
https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia#nvidia%253Fstate%253Dclosed (https://code.google.com/p/tc-ext-tools/source/browse/packages/nvidia#nvidia%253Fstate%253Dclosed)
-
I installed the nouveau driver and I'm now getting the error "failed on WaitforX". I'm not sure if I need to specify something in order for X to start or if I should remove the driver. I don't know how to remove the driver from the command line. At least I know I can get into X with the generic driver. Is there an option I should try from here? If not, how can I remove this driver from the command line?
Regards from the Lynx browser,
Thank you
-
Hi ECHOSIDE
You could remove the nouveau entry from your onboot.lst file.