LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-28-2013, 04:34 AM   #1
NaTTaN
LQ Newbie
 
Registered: Jun 2011
Location: user land
Distribution: Slackware 14
Posts: 28

Rep: Reputation: Disabled
problems with KDE/XFCE/Fluxbox and graphical interfaces....


Hi, had a lot of time without coming to the forum, am having problems with the Desktop Environments(KDE, Fluxbox, XFCE) after i upgraded from 2.3.26 kernel to the 2.3.45, i want to make clear that am not getting any black screen, everything is ok until i execute startx on the console or i try to use any application like firefox,mplayer or libreoffice...

The system gets frozen and the only thing that stays working is the mouse pointer... i can't even open any TTY.


greetings,
NaTTaN
 
Old 05-28-2013, 09:26 AM   #2
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}, FreeBSD
Posts: 206

Rep: Reputation: 112Reputation: 112
Quote:
Originally Posted by NaTTaN View Post
The system gets frozen and the only thing that stays working is the mouse pointer... i can't even open any TTY.
Hi,

that's what happened to me, among other things, after upgrading. You probably looked at this thread already, but I suggest you to go back there and skip the first 3 pages, starting reading from ruario's post #48: in fact the topic changed slightly, as several of us had a different issue that could be solved with kernel 3.4.47 (using config from testing) or kernel 3.8.13 from current.

Best regards,
Philip
 
Old 05-29-2013, 04:25 PM   #3
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,876

Rep: Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927
Yep that sounds exactly like the problems I and several others where facing. It looks like Pat is considering another kernel update.

Quote:
Originally Posted by volkerdi View Post
Is this with Intel graphics again?

I've been pointed to another suspicious commit and might be forced to do a third build. Giving much credit to whether a kernel series is designated LTS isn't looking like it matters as much as we may have thought. If 3.2.x had been dead, we'd have patched the CVE and had it right the first time.
You might want to comment in that thread as well and confirm if you do have an Intel graphics card as Pat appears to be actively following that thread but may not have seen this one.

If you cannot wait for a fix I would do as Philip suggests and try with either the 3.4.47 or 3.8.13 kernels. If you have never built a kernel before you should read "Building a Linux Kernel from Source" from the Slackware Documentation Project.

You can get Pat's config files for the 3.4.X series of kernels in slackware-14.0/testing/source/config-testing-3.4.11/. Alternatively the 3.8.X series of kernels config files can be found in slackware-current/source/k/.

Kernel source packages for both of these kernels can be obtained from www.kernel.org.
 
Old 05-29-2013, 04:48 PM   #4
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,876

Rep: Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927
By the way you could use the binary kernel packages from -current directly on 14.0 but keep in mind this comment

Quote:
Originally Posted by volkerdi View Post
You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.
As it happens I was able to use the binary kernel packages from -current on 14.0 and successfully recompile the VirtualBox kernel module (which even worked) but I wouldn't count on being able to do so.

If you don't need to compile your own modules however, this won't be an issue.
 
Old 05-31-2013, 07:29 AM   #5
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,876

Rep: Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927Reputation: 927
From the other thread:

Quote:
Originally Posted by volkerdi View Post
This might be the cause:

https://git.kernel.org/cgit/linux/ke...dc11b95adc339c

I'm considering doing a third build. If anyone who is running into problems still could revert this patch and rebuild to see if it fixes the issue, then I'd do it for sure. The only Intel graphics I have here are the trusty GM945, and there's no problem there.
This does indeed appear to be the cause as both Philip and myself have rebuilt 3.2.45 with that patch removed and the issues have gone away. If you are not sure how to revert the patch by fetching it from kernel.org and issuing a reverse patch command, in this particular case you can easily do it manually (since it is only additional code added in one block). Philip explained how in the other thread. Basically you open /usr/src/linux-3.2.45/drivers/gpu/drm/i915/intel_ringbuffer.c in a text editor, locate and then remove the following section:

Code:
        /* Required for the hardware to program scanline values for waiting */
        if (INTEL_INFO(dev)->gen == 6)
                I915_WRITE(GFX_MODE,
                           GFX_MODE_ENABLE(GFX_TLB_INVALIDATE_ALWAYS));
A quick summary to rebuild the kernel would be to first make sure the very latest Slackware provided 3.2.45 kernel-source package is installed, switch to root, cd into /usr/src/linux-3.2.45, correct the drivers/gpu/drm/i915/intel_ringbuffer.c file (as explained above), then issue the following:

Code:
make oldconfig
make bzImage modules
make modules_install
When this is complete, copy arch/x86/boot/bzImage into boot with an appropriate name (and optionally do the same with System.map and .config), then make an initrd as per /boot/README.initrd and rerun lilo (possibly after first editing /etc/lilo.conf if needed). You should now be able to reboot into your patched kernel.

If you want to make your own packages for your patched kernel have a look at the SlackBuilds in the packaging directories in slackware-14.0/source/k/ (a quick read through will show you how they work).

Finally, if you want to clean up your /usr/src/linux-3.2.45/, cd back into it and issue the following:
Code:
make clean
make prepare
rm .version

Last edited by ruario; 05-31-2013 at 07:52 AM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NETBOOKS: what Mint: LXDE or Fluxbox? (or KDE or XFCE) Timmi Linux Mint 47 10-16-2010 11:14 AM
[SOLVED] How would I swap window managers from KDE to Fluxbox or XFCE? Lanteran Slackware 2 06-09-2010 04:18 PM
openoffice 1.1.4 killed in gnome and xfce but not kde and fluxbox carboncopy Slackware 2 01-27-2005 03:33 AM
Mandrake graphical interfaces (getting to them) qUox Linux - Newbie 2 10-12-2004 09:06 PM
xfce switching between graphical interfaces el_pajaro! Linux - Software 3 09-10-2004 12:32 PM


All times are GMT -5. The time now is 05:21 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration