Slackware 13.0 with KDE 3.5.10?
in [Slackware]
|
Prev: useradd, upgrading Feunster
Next: Qemu help
From: Tuxedo on 1 Jan 2010 03:47 Murat D. Kadirov wrote: > On Thu, Dec 31, 2009 at 08:37:23PM +0100, Tuxedo wrote: >> Again, anyone who happens to have a functional xorg example or just the >> relevants parts that define DRI and who can post them here would be most >> helpful. The type of hardware used is an Intel on-board 82852/8255 GM >> Graphics Controller and screen 1024x768 True Color (60 Hz). Although in >> the display preferences in KDE as well as XFCE can be toggled up to 85 Hz >> and of course various values below. > > I suggest upgrade your kernel to 2.6.31/32. AFAIK, 2.6.29 kernel has many > problems with Intel drivers in Linux. Upgrading to the 2.6.31 has helped > me with frequent Xorg' crashes after resume from suspend-to-ram. I have: > > root(a)apollo:/home/murat# lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME > Express Integrated Graphics Controller (rev 03) > > But anyway, I think upgrading will help you. 2.6.29 kernel was bad > kernel in many way and it does not supported anymore. > Thanks for the tip, upgrading to kernel 2.6.31/32 sound worth a try! As a user, I've never had a need to change a kernel before, so however simple it may sound to some people on this group, I would have no idea how! What is the best or easiest procedure to install and test an alternate kernel? For starters, where can I find the actual kernel? The way I installed the current system was by creating a bootable USB media using UNetbootin (http://unetbootin.sourceforge.net). An excellent tool btw. It includes the option of defining a path to a custom kernel. My newly installed Slackware 12.2, which works extremely well in comparison to any other distro I've tested, now has kernel 2.6.27.7: bash-3.1# uname -a Linux q25 2.6.27.7 #1 Mon Dec 8 15:21:42 CST 2008 i686 Intel(R) Pentium(R) M processor 1.60GHz GenuineIntel GNU/Linux Tuxedo
From: Henrik Carlqvist on 1 Jan 2010 06:52 Tuxedo <tuxedo(a)mailinator.com> wrote: > Murat D. Kadirov wrote: >> I suggest upgrade your kernel to 2.6.31/32. > I've never had a need to change a kernel before, so however simple it > may sound to some people on this group, I would have no idea how! Downloading a kernel from kernel.org and compiling it with reused settings from /boot/config to .config might not be so hard. Also installing all the modules included with the kernel is easy. However, after this is done some problems may remain. Maybe some kernel modules are missing because they were not part of the kernel package but instead came from other packages like X, alsa or some kind of binary drivers. Also those modules will have to be tracked down and recompiled. I don't know how many such modulers there is in Slackware 13, but I know there have been such modules in earlier versions of Slackare. Then with a new kernel you will have a glibc which doesn't match your current kernel. In most cases this is not a problem, but at least in teory it could lead to problems. So instead of upgrading the kernel I would suggest to upgrade or downgrade the entire distribution to a version that works fine. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Tuxedo on 1 Jan 2010 10:39 Henrik Carlqvist wrote: [...] > > So instead of upgrading the kernel I would suggest to upgrade or downgrade > the entire distribution to a version that works fine. Yes, sticking with a kernel that comes with an installed Slackware version and then somehow making the Intel graphics work with DRI sounds like the potentially "easier" option for me compered with updating the kernel. Tuxedo
From: Grant on 1 Jan 2010 14:28 On Fri, 01 Jan 2010 12:52:12 +0100, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote: >Tuxedo <tuxedo(a)mailinator.com> wrote: >> Murat D. Kadirov wrote: >>> I suggest upgrade your kernel to 2.6.31/32. > >> I've never had a need to change a kernel before, so however simple it >> may sound to some people on this group, I would have no idea how! > >Downloading a kernel from kernel.org and compiling it with reused settings >from /boot/config to .config might not be so hard. Also installing all the >modules included with the kernel is easy. > >However, after this is done some problems may remain. Maybe some kernel >modules are missing because they were not part of the kernel package but >instead came from other packages like X, alsa or some kind of binary >drivers. Also those modules will have to be tracked down and recompiled. I >don't know how many such modulers there is in Slackware 13, but I know >there have been such modules in earlier versions of Slackare. Huh? Maybe back in the pre 2.4 series days? > >Then with a new kernel you will have a glibc which doesn't match your >current kernel. In most cases this is not a problem, but at least in teory >it could lead to problems. No, upgrading the kernel doesn't change glibc at all. > >So instead of upgrading the kernel I would suggest to upgrade or downgrade >the entire distribution to a version that works fine. Er, no. Running the latest kernel is easy, I've been doing it for many years. First thing I do after a new slack install is upgrade to latest kernel. Only exception to running latest is on slack-11 box where I'm running 2.6.27.42 (2.6.27 is extended maintenance release kernel) to avoid updgrading iptables user-space. Usually only the latest and latest-1 kernel releases are maintained, this means you may have security or other issues with older kernels. Grant. -- http://bugs.id.au
From: Grant on 1 Jan 2010 14:30
On Fri, 1 Jan 2010 16:39:28 +0100, Tuxedo <tuxedo(a)mailinator.com> wrote: >Henrik Carlqvist wrote: > >[...] > >> >> So instead of upgrading the kernel I would suggest to upgrade or downgrade >> the entire distribution to a version that works fine. > >Yes, sticking with a kernel that comes with an installed Slackware version >and then somehow making the Intel graphics work with DRI sounds like the >potentially "easier" option for me compered with updating the kernel. You're being wimpish about upgrading kernel ;) Kernel Intel driver fixed in later kernel. So wait for slack-13.1? Grant. -- http://bugs.id.au |