SliTaz Forum » Forum: Support - Recent Posts

stinco on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

stinco — Wed, 22 May 2013 03:18:42 +0000

Eureka!!! I've got 1152x864 resolution!

Wrap-up:

To get to the desired 1152x864 screen resolution, there were 2 problems that had to be solved.

1. Change the default color depth from 24 to 16 to allow the available video RAM (2Mb) to accomodate a maximum resolution of 1152x864 instead of 832x624.

2. With default color depth changed to 16, change the virtual screen size from 1024x768 to 1152x864.

The first problem was solved by adding the statement "DefaultDepth 16" to the xorg configuration file /etc/X11/xorg.conf.d/70-Screen.conf, as shown below:

>
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
EndSection
>

Note: The Display SubSection for Depth 24 was removed.

After reboot, the default color depth had indeed changed from 24 to 16 giving an immediate increase in screen resolution from 832x624 to 1024x768.

The second problem was solved by the following 2 steps:

1. Creating a 1152x864 Modeline in a terminal session with "gtf 1152 864 75". The Modeline statement was then copied into the configuration file /etc/X11/xorg.conf.d/50-Monitor.conf as shown below:

>
Section "Monitor"
#DisplaySize 320 240 # mm
Identifier "Monitor0"
VendorName "VPR"
ModelName "vpr Matrix"
HorizSync 30.0 - 96.0
VertRefresh 50.0 - 160.0
Modeline "1152x864_75.00" 104.99 1152 1224 1352 1552 864 865 868 902 -HSync +Vsync
Option "DPMS"
EndSection
>

2. Adding 'Modes "1152x864"' statement to the configuration file /etc/X11/xorg.conf.d/70-Screen.conf. Note that this is the 2nd change to this file. Shown below:

That's it!

Many thanks to Trixar_za for getting me on the right track.

stinco on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

stinco — Mon, 20 May 2013 04:49:18 +0000

Hello Trixar_za,

OK, back from internet isolation. Did what you said and changed the Screen section file "70-Screen.conf" from:

>
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
>

To:

Notice that I also removed the Display subsection for "Depth 24".

The change did in fact set the color depth to 16 just like you said, and the default screen resolution was raised from 832x624 to 1024x768, but I want to get 1152x864 as is available in Slitaz 3.0 and other distros. Looking at the log file, I noticed that 1152x864 is rejected because of "height too large for virtual size" as seen in the following lines from the log file:

>
[ 47.439] (WW) MACH64(0): Shrinking virtual size estimate from 2048x1536 to 1024x768
[ 47.439] (II) MACH64(0): Not using default mode "1152x864" (height too large for virtual size)
[ 47.441] (--) MACH64(0): Virtual size is 1024x768 (pitch 1024)
>

In Slitaz 3.0 and using MACH64 driver, the "virtual size" gets set to 1152x864, so it isn't an issue of insufficient memory. Sorry about uploader removing tabs from the Screen section portions.

Trixar_za on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

Trixar_za — Tue, 14 May 2013 21:25:37 +0000

Probably because configuring xorg is a little different in this version of it. You have to modify the conf files in /etc/X11/xorg.conf.d/ which are in themselves just split up sections of the old xorg.conf file from before. You probably should put the stuff you used in the Screen section in the 70-Screen.conf file instead.

stinco on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

stinco — Tue, 14 May 2013 16:09:47 +0000

Hello Trixar_za,

Thanks for the reply. Yep, before my original post I had already used tazx to install the correct driver (MACH64), and gotten basically the same result. The big difference was that the maximum screen resolution is 832x624 with MACH64. The color depth remained the default 24, instead of the 16 that I had specified in xorg.conf. Using Slitaz 3.0, I'm able to get 1024x768 with the default driver (VESA) and 1152x864 with MACH64 by just adding the "DefaultDepth 16" statement to the "Screen" section of xorg.conf. I'm doing a certain amount of guessing here, but I'm guessing that the problem isn't the driver.

I'll have flakey (or no) internet access from 5/15-5/19, so will probably be out of touch until 5/20..

Trixar_za on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

Trixar_za — Tue, 14 May 2013 10:31:29 +0000

The default driver tends to ignore xorg.conf changes, so it's better to install the right video driver using tazx from the terminal while online. Then just restart and Xorg should reconfigure itself automatically.

stinco on "Max Screen Resolution 800x600 in Slitaz 4.0 ?"

stinco — Mon, 13 May 2013 06:42:18 +0000

Hello Slitaz Gang,

I think I have found out what has been happening to some Slitaz 4.0 users, who are stuck at maximum 800x600 screen resolution. I have had the same problem with an IBM Aptiva, yet using the same PC, I'm able to get higher screen resolution with Slitaz 3.0. Without going into a long winded explanation as to how I found out, in Slitaz 4.0, THE XORG.CONF DefaultDepth STATEMENT IS BEING IGNORED. It is being handled correctly in Slitaz 3.0. I used the X server log (/var/log/Xorg.0.log) to see what was going on. For those who may be wondering why I'm talking about DefaultDepth, maximum screen resolution is determined using color depth (DefaultDepth) and the amount of video RAM. By specifying a lower color depth, like 16 instead of 24, more screen pixels can be contained by the available video RAM. In the posts that I saw complaining about the 800x600 problem, the posters didn't say anything about the hardware that they were using. I'll guess that they were using old low spec PCs with 2Mb of video RAM (like my Aptiva).

------------------------

IBM Aptiva, 266MHz AMD K6-2, 256Mb memory, ATI Technologies Inc 3D Rage Pro AGP 1X with 2Mb video RAM (On motherboard)

kultex on "Rolling ISO vs Cooking ISO"

kultex — Sat, 09 Mar 2013 12:10:26 +0000

The is no more daily - the last is from 22.2.

http://mirror.slitaz.org/iso/rolling/

and it is not really to use - there will be changes in the kernel........

oui on "Rolling ISO vs Cooking ISO"

oui — Sat, 09 Mar 2013 12:02:21 +0000

where is the download url of the daily slitaz rolling iso (alone, without all packages!!! it is silly dilly to download 3,4 GB only to constate you can't make X.org operable actually!)?

ernia on "Assign a Custom Icon to an Executable"

ernia — Sat, 05 Jan 2013 07:44:24 +0000

.desktop files in /usr/share/applications should produce an incon in the Applications menu, in the left down corner of the screen.
check where your minecraft icon is or the syntax of your file.

Supernurd on "Assign a Custom Icon to an Executable"

Supernurd — Sat, 05 Jan 2013 06:00:12 +0000

Oh nevermind, I just made a typo. I was able to open it from the usr/share/applications directory. Thanks for being so helpful.

Supernurd on "Assign a Custom Icon to an Executable"

Supernurd — Sat, 05 Jan 2013 05:57:30 +0000

Alright, so I have my Minecraft.desktop file created, but where do I go from here? Have I just essentially just created an application? And how do I open this application?

Supernurd on "Assign a Custom Icon to an Executable"

Supernurd — Sat, 05 Jan 2013 05:31:18 +0000

Thank you, that did actually make a lot of sense. I love the intimate feeling that you end up having with your personal linux OS, especially a barebones redist like Slitaz because you put so much work into every detail. Thanks a lot.

gdesilva on "Assign a Custom Icon to an Executable"

gdesilva — Sat, 05 Jan 2013 01:19:32 +0000

Go to /usr/share/applications directory where you will find <app-name>.desktop files. You can use leafpad to edit any one of them to see how various apps are invoked from desktop. I would create a minecraft.desktop (or call it something else if it already exists or rename the existing one to some other name) and invoke your script under 'exec' line and specify your own image in 'icon' field. Hope this makes sense. Also make sure you create this file with appropriate permissions - ie set the permissions as in the case with other .desktop files.

Supernurd on "Assign a Custom Icon to an Executable"

Supernurd — Fri, 04 Jan 2013 21:46:41 +0000

I am a major noob, I hear you get a lot of those around here ;) I looked around the forum for a while without finding this topic so I made an account just to ask the question. I also didn't really know which forum to post it in, so I apologize if someone ends up having to move it.

Well I created a text file with the following code and then made it executable using the "properties" tool in the drop-down menu:

"
cd /home/tux
java -cp minecraft.jar net.minecraft.LauncherFrame
"

As you may have noticed, it is just a simple shortcut to open Minecraft. As it is an executable, the icon has an image of a shiny silver gear, but I want to change it to the Minecraft icon.

I've opened up the icon viewer and found where all the icon .png's are stored. I also noticed that the executable is considered to be an "application-x-executable" mimetype (if you could also explain what a mimetype is that would be useful ;))

So I suppose my question is, is there some way to make a custom mimetype, assign my desired icon to it, and then change my shortcut to that mimetype?
-OR-
Am I missing something entirely and this is all really very simple?

jjk on "Slitaz live cd - no gui "

jjk — Mon, 17 Dec 2012 17:43:10 +0000

I've pretty much the same problem, how did you exactly fix this, i tried the fixes described in the posts above. boot with screen=text and nomodeset run tazx install xorg, install nv driver (i got nvidia video card, vesa driver has same problem, tried that too). it gives error: "screen number doesn't match or something". what should i do?