SliTaz Forum
You are not logged in.
I have tried out quite a few Linux distro's but i always keep comming back to Slitaz. And the only reason that i have not installed Slitaz to the hard-drive is because i cannot configure the screen resolution from the default value of 800x600 pixels to something like 1024x768 pixels. Could someone help me please?
Offline
hi loner,
You need the right Xorg driver to have a better resolution. For that you can use 'tazx install-xorg'. Loading the right kernel modules & restarting Xorg, or rebooting is needed. If better resolution is not setted up automaticaly – which's always the cases when you don't reboot – you can do it manually using xrandr (pkg: xorg-xrandr) or lxrandr (only with cooking). You can use 'tazlito writeiso' to generate a liveCD including the driver: A cleaner way is to use flavors: http://doc.slitaz.org/en:handbook:genlivecd
I opened a terminal and typed: xrandr and from the output i saw that there were only two options, which were: 800 x 600 and 640 x 480. So unless this issue is addressed in the next stable release of Slitaz which will be Slitaz-4.0? Then user's like myself will not be using Slitaz which will be a great shame.
Offline
As I said you have to install the good Xorg driver.
Make sure you're online and then do the following:
1. Go to terminal
2. Type su and press enter/return
3. Enter your root password and press enter/return
4. Type tazhw detect-pci and press enter/return
5. Type tazx and press enter/return
6. Pick xorg Install or Reconfigure Xorg and click OK.
7. Allow it to download the package lists, then pick the card type closest to your own and click OK.
8. Allow it to go through all that setting stuff and then close the box.
9a. For Stable: Now in terminal type wget http://www.trixarian.za.net/downloads/lxrandr.tazpkg then type tazpkg install lxrandr.tazpkg and press enter/return
9b. For Cooking: Type tazpkg get-install lxrandr.tazpkg
10. Go to Red Spider Button---> Preferences---> Monitor Settings to change your resolution.
Offline
Hi Trixar_za i followed your tutorial without an hitch but when i went to:
The Red Spider Button => Preferences => Monitor Settings all i got was: Unable to get monitor information!
Offline
I forgot to mention you have to install the xorg-xrandr package for lxrandr to work properly. So just add the additional step of going tazpkg get-install xorg-xrandr to the above.
Offline
hey guys,
all done as detailed above with no changes.
I know my machine has an ATI rage if that could help.
Fujitsu Lifebook C6611
PIII 900mhz
Still stuck at 800
Thanks
Offline
Maybe you could help us out a bit more and tell us which ATI Rage card you have. For example with ATI Rage 128, you need to use modprobe -v r128 but it varies from card to card. Normally the tazhw --detect-pci should automatically detect and load this kind of module, but sometimes it does fail.
Offline
this is what I got with tazhw
Detected pci kernal modules
snd_intel8x0
snd_intel8x0m
yenta_socket
yenta_socket
I dont see anything video related there, am i mistaken?
Offline
AGP - ATI RAGE Mobility P
Offline
Follow my instructions here:
http://vanilla.slitaz.org/index.php?p=/discussion/comment/12674#Comment_12674
Offline
I tried with no success. But I may be confused here.
Do i install everything in order as per instructions
or
only what is indicated as in
"install linux-agp.tazpkg" for the intel card
or
"install xorg-xf86-video-ati-6.9.0.tazplg" for ati card
In the Device area my driver shows up as Versa (or something like that)
Install linux-agp.tazpkg for:
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
Add intel_agp to /etc/rcS.conf LOAD_MODULES=
Install: xorg-xf86-video-ati-6.9.0.tazpkg
For: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
Kill the xserver (Ctrl+Alt+bkspace)
Login as root pw: root
tazx
choose reconfigure xserver
ok
reboot
You should be able to get 1024x768 resolution
If this fails open /etc/X11/xorg.conf
Should see:
Section "Device"
Driver "ati"
Offline
same here; after I reset everything, it went back vesa
[c]Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/X11/modules"
FontPath "/usr/share/fonts/X11/misc/"
FontPath "/usr/share/fonts/X11/TTF/"
FontPath "/usr/share/fonts/X11/OTF"
FontPath "/usr/share/fonts/X11/Type1/"
FontPath "/usr/share/fonts/X11/100dpi/"
FontPath "/usr/share/fonts/X11/75dpi/"
EndSection
Section "Module"
Load "glx"
Load "dbe"
Load "dri"
Load "extmod"
Load "freetype"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
VendorName "Unknown Vendor"
BoardName "Unknown Board"
BusID "PCI:1:0:0"
EndSection
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
[/c]
Offline
Hi All
I managed to make it work! I installed the Mach64 driver, did tazx and rebooted.
labs.slitaz.org/attachments/139/xorg-xf86-video-mach64-6.8.0.tazpkg
Offline
Gonna try that tomorrow, thanks.
Offline
is there any chance that in 4.0 this recurring issue will be automated?
Offline
I have had a similar problem with slitaz stable 3.0 and even the latest cooking version. With the xvesa version of slitaz stable 3.0, I was able to choose resolutions greater than 800x600.
Offline
Is there an xvesa version for slitaz cooking?
Offline
xvesa version seems to be working for me. But only the second time I booted with the Cd.
Offline
Only with the xvesa version of slitaz stable 3.0 am I able to choose a resolution greater tha 800x600. As far as I can tell there is no xvesa version of slitaz cooking. Also, with the xorg version of slitaz stable 3.0, in addition to the resolution isssue, I have the terrible problem of the "X" cursor erasing portions of the screen image as it is moved across the screen. This is not a problem with slitaz cooking, but I would like to have an xvesa version of slitaz cooking so I could use a resolution greater than 800x600.
Offline
There might be a issue with making a SliTaz 4 Xvesa flavour because Xvesa has been discontinued by it's developers in favour of X.org or so I've heard. We can still create a Xvesa flavour, but some newer cards support will fall to the way side.
Offline
Okay, too bad, thanks.
Offline
xvesa version definitely made the diference and is stable.
Offline
I also have been bothered by the lack of easily set screen resolutions and the fact that almost all linux distros ( and Slitaz seems headed this way) seem to be set to come up in the highest screen resolution supported. Why not 1.) have an easy to use GUI appplication to set the monitor resolution in X-window once booted, 2.) Also why not come up in 800x600 or 1024x768 so that people with smaller monitors do not have to get a magnifying glass to read the screen. Having an easy way to set screen resolution is something most other linux distros have in an easy to find menu item.
I hope that when 4.0 stable comes out, if not before, that something is done about selecting X-window screen resolution to make it easy and much less painfull.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]