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 have an computer it use "Intel Graphics Media Accelerator 3600 Series". I installed Slackware 13 (Kernel: 2.6.36.1). This computer have extended display (2nd Display). But I cannot setting for dual display. And I think this problem at driver of Graphic Adapter.
I found this driver "http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2" at https://01.org/linuxgraphics/downloads. But I don't know how to install.
IMO this rule out using this chipset on Slackware 13.
So I would suggest that you just install Slackware 14.1 and follow the instructions on aforementioned page beginning with "Kernel module driver". Don't even try to use the driver provided by Intel, but just the one in the kernel. You will get less features but it will be a lot easier to have it working.
Mon Jan 9 2012 - v1.0
======================
In the Beta and Alpha releases of the PVR Cedartrail driver, ports were bundled
for differing Kernel and Mesa/Xorg combinations. As of the version 1.0 (v1.0)
release, the only supported driver targets are for:
* Kernel 3.0.0
* Mesa 7.9
* Xorg 1.9
Driver support for the following targets has been _dropped_ as of v1.0:
* Kernel 2.6.38
* Mesa 7.10
* Xorg 1.10
But Slackware 13 includes older versions, so you would have to replace all these major components and that's very hard to do.
Furthermore as said in INSTALL after that you would have to patch and rebuild your kernel then install specific userspace components.
All that hard work without any guarantee of success.
You can try to follow the instructions in aforementioned documents, but honestly you would probably just loose your time.
But this could be a painful process because it is not possible to do it at once. You would have to perform several successive upgrades:
13 => 13.1
13.1 => 13.37
13.37 => 14.0
14.0 => 14.1
So it will take some time and you will need to follow very carefully the instructions at each step.
That is why personally I would much prefer in your case to install Slackware 14.1 from scratch as also advised in this document: overall it is a lot faster and less risky, provided that you have a mean to make a backup of all your the data you care about before you begin. Then you will just have to restore these data after having installed your new system.
You will just have to take the time to carefully list all these data you don't want to loose: basically probably files in your /home directory, maybe other archives stored elsewhere and possibly databases stored e.g. in /var/lib.
We can help you to do that and also to find the best way to make your back up if you tell us what storage space you can make use of, be it locally or remotely (of course ability to store on an external disk can help a lot).
Even if your machine acts as a server that has to run most of the time, overall this way is safer and will occasion less down time.
You can also do a practice migration with a VM. Virtualbox is free and you can install Slack 14.1 in there. Then you find out what you'll need to do to get it close to your current install. This would include adapting any configs from 13.0 to 14.1 if needed, copying databases/website code, compiling 3rd-party programs (then save the packages so they can easily be installed on your computer when you do the real migration).
VMs make great practice machines. You could also, if really desired, install 13.0 and then perform all the upgrades that Didier pointed out, if you want to take a ton of time attempting that.
But I totally agree with Didier that it is better to just do a clean install of 14.1.
Usually if you have all your user data in /home on a separate partition, migration is relatively painless. Just reformat the other partitions, remount the /home partition, and recreate the users and groups after installing 14.1. Software from SBo and such will have to be rebuilt, but it's an investment after all.
Keep in mind that even if you upgrade to a newer Slackware version, Linux support for the GMA3600 (which is a relabeled PowerVR SGX545) is still abysmal, you will get only very basic functionality.
As sad as it is, this machine is best used with Windows.
This may sound off kilter but I remember reading that the omap SoC chips used the SGX series GPUs.
Has any effort been done to test the omap drivers against the SGX series to see if it might offer some support? I think libdrm and xorg had options to support omap chips on some level. I do not however recall Mesa having any support for omap hardware, if it is, it might be buried in another driver like ilo, but I'm only guessing here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.