[SOLVED] system upgraded to -current; GUI still not right
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Slackware not "reading" my processor in-built graphics chip?
1. KDE will open cleanly only in "failsafe" mode.
2. Xfce & other options will not open cleanly at all.
3. Tried to install Salix 14 and got same fragmentation.
4. Mint running like mint.
5. Install media is not corrupt.
6. Changed back to older screen and got exactly same resutls as at 1 thru to 5 above.
Do you see differences in /var/log/Xorg.0.log from Mint when compared to Slackware and Salix?
The output from that log is so voluminous that I haven't yet dared to compare, besides which, I confess, there seems to be so much repetition and apparent redundancy in the log (i stress: apparent) that I can't make head nor tail of it.
However, as your post implies, I must nut it out, if I am to get anywhere.
Thanks for bringing me back to the obvious: I'll do it and get back to this thread tomorrow.
I don't think allend meant that you need to reinstall anything.
If you start at runlevel 3 (console mode), type 'xwmconfig' to chose another DE or WM (tnan KDE) vbefore running 'startx'.
If you start in runlevel 4, choose another DE or WM clicking the arrow (IIRC).
Did i thank you for this, Didier?
If not: merci beaucoup; c'est tres gentil et tres perspicace de vous de me le signaler.
Amicalement,
Tex (australien de souche, pourtant un qui se passionne pour le francais)
Poste Scriptum:
I tried your suggestion; malheureusement, je reste toujours dans le petrin!
Allend continues - heroiquement!- to help me get to the bottom of this problem, as a glance at page 2 (!!??) of this thread will reveal: we are deep in Xorg logs.....
Last edited by textillis; 06-20-2013 at 11:59 PM.
Reason: additions
Your Mint install is using X.Org X Server 1.13.0 and kernel 3.5.0-17, which are later versions than in Slackware 14.0 which is using X.Org X Server 1.12.3 and kernel 3.2.29 ( or X.Org X Server 1.12.4 and kernel 3.2.45 if fully patched).
Slackware 14.0 included newer versions of libdrm and X video drivers for intel in /testing.
From README.TXT
Quote:
| | Finally, there are newer versions of libdrm and
| | the X video drivers nouveau, ati, and intel.
| | These alternate drivers require the libdrm
| | update, so be sure to install that if you try
| | them. These weren't included in the main tree
| | because Mesa is not yet compile-ready for this
| | version of libdrm.
You could try installing these.
Alternatively, you could consider upgrading to Slackware-current which is using X.Org X Server 1.13.4 and kernel 3.9.5
Your Mint install is using X.Org X Server 1.13.0 and kernel 3.5.0-17, which are later versions than in Slackware 14.0 which is using X.Org X Server 1.12.3 and kernel 3.2.29 ( or X.Org X Server 1.12.4 and kernel 3.2.45 if fully patched).
Slackware 14.0 included newer versions of libdrm and X video drivers for intel in /testing.
From README.TXT
You could try installing these.
Alternatively, you could consider upgrading to Slackware-current which is using X.Org X Server 1.13.4 and kernel 3.9.5
Thanks Allend.
I would have acted on your suggestion regarding "current" but for the fact that I'm having difficulty reading anything or navigating around my slack 14 install; but this has given me an idea to try.
Again, many thanks; I really appreciate your time in looking at this and responding so informatively and rapidly. Big respect.
Edit: course, it just occured to me: i don't need to go into gui to upgrade to -current ....
Now I got me marching orders!
(I'll let you know how it goes)
Yes, you gave me a reputation point that actually allend deserved
OT: to type accented characters using an English keyboard, press together Ctrl+Shift+u, release these three keys then type the four hex digits of the UTF-8 code of the character.
Yes, you gave me a reputation point that actually allend deserved
OT: to type accented characters using an English keyboard, press together Ctrl+Shift+u, release these three keys then type the four hex digits of the UTF-8 code of the character.
That works in LQ's post editor.
Of course, I remember. Thanks for the reminder. Where can I find a list of the codes by the way?
Place the following content in
a file at /etc/X11/xorg.conf.d/disable-composite.conf:
Section "Extensions"
Option "Composite" "Disable"
EndSection[/code]
If an alternative window manager fails, then it may be a problem with X. The output from /var/log/Xorg.0.log can help here.
Aside- This 'Mexican' says to watch out for banana benders!
Hi Allend, I tried this last night with high hopes, to no effect.
Just to check I have understood:
do I place the text, exactly as is written above, inclusive of "Section ... EndSection"? In other words: everything, as is, between the full-colon and end code brackets, in a config file which I create, then place in /etc/X11 directory?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.