SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm experiencing problems loading to level 4. It seems that 1024x768 is a resolution too high. I want to load to level 4 at a resolution of 800x600. How can I configure slackware to do so? I'm running slackware 14.1 on a pentium 3.
Use krandrtray (right click on the screen widget in the tray to pick one of the available resolutions).
You need to have the KDE series of packages installed, but do not need to run KDE. For instance this works here under Fluxbox.
Hello Mr. Didier,
I cannot run anything in GUI mode for now ( level 4 ). When I run krandrtray in command line it doesnt work, I'm guessing this works in level 4 mode right? I'm wundering if you know how to configure slackware 14.1 to use a 800x600 resolution, to be configured if possible in command line mode, or level 3 mode... I use startx to go to level 4 mode and the screen freezes, I cant do anything in GUI mode cuz it doesnt print correctly on the screen.
I tried xorgsetup, and it allows me to choose the depth, which I selected 8 bit, but it doesnt allow me to choose the screen resolution. The command xorgconfig doesnt work, I think the correct command is xorgsetup...
Any idea on which file I have to edit to say to the X server to select a specific screen resolution? I saw xorg.conf-vesa and theres the refresh rate, but I dont want to play with that cuz I dont want to brake my monitor (= Plus I dont know what is the refresh rate for 800x600 resolution.
You can also take a look at /etc/lilo.conf and change your framebuffer settings from 1024 to 800x600, that is, comment out 1024 and remove the # in front of 800x600x256. That might help. Sometimes if your framebuffer isn't set-up properly then x windows will have difficulties.
You can also take a look at /etc/lilo.conf and change your framebuffer settings from 1024 to 800x600, that is, comment out 1024 and remove the # in front of 800x600x256. That might help. Sometimes if your framebuffer isn't set-up properly then x windows will have difficulties.
Thanks my friend, I'm rebooting as we speak to try it out. I'll keep you posted.
Cheers,
Dumdadum
Nope, that only helped the command line resolution. I tried loading with startx and its still in 1024x768...
Waiting for your reply,
Cheers,
Dumdadum
Last edited by dumdadum; 07-04-2014 at 09:55 AM.
Reason: update on result with lilo.conf edited
cd /etc/X11
cp xorg.conf-vesa xorg.conf
sed -i 's/Modes "1024x768"/Modes/g' xorg.conf
then as regular user run xwmconfig and if not already done choose fluxbox as windows manager, then type startx and let us know how that goes.
Hello Mr. Didier, here is the result. What I did is execute the 3 commands you gave me, executed xwmconfig and selected razor-qt instead of fluxbox and rebooted the system. Here is what I get, it loops, cannot load the login manager, and advises that the boot process is halted and freezed for 5 minutes... here is the printing on the screen, I was able to copy paste it in a text file for you to analyze:
Code:
Loading extension GLX
vesa: Ignoring device with a bound kernel driver
(EE)
Fatal server error:
(EE) no screens found(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional inf$
(EE)
(EE) Server terminated with error (1). Closing log file.
INIT: Id "x1" respawning too fast: disabled for 5 minutes
What is wrong? Why wont it work? Can you give me more help please?
First, till we sort out this issue please start your system in runlevel 3 to avoid this:
Code:
INIT: Id "x1" respawning too fast: disabled for 5 minutes
as according to this line from /etc/inittab
Code:
x1:4:respawn:/etc/rc.d/rc.4
this occurs only in runlevel 4.
Now, let's try to understand why the vesa X driver refuses to cooperate.
For that, please provide output of following commands typed as root:
Code:
lsmod
lspci -knn|grep -A2 VGA
Ok Mr. Didier, will do...
I have a little question... cant I edit a file manually, I'm just guessing maybe the xorg.conf or xorg.conf-vesa and configure them to load only "800x600" video modes? I'm asking cuz if there were such a file I have no clue its which one...
I'll try what you said and post output as you requested.
Thanks again,
Dumdadum
Euh, Mr. Didier, when I put myself in level 3 in the inittab and load manually with startx logged in with the root user it load xfce, cuz I just chose xfce with xwmconfig and not fluxbox, the resolution is! in 800x600... thing is that its all blury, the colors dont print well, I cant even see the menu when I click on the application menu button on the bar, I cant see the icons well neither... Can you help with that please?
I'll post the output of the 2 commands you asked me, as soon as I find a free usbkey here at the office.
Thanks again,
Dumdadum
==
Here Mr.Didier is the output of the two files you so kindly requested:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.