So I've installed Slackware on an old PC
It is very very old, I can't check it right now because the installation proccess is still going on. From what I've recall it is an AMD Duron, Sis or Via graphic card, 384 MB. The problem is: what now? What do I do with this?
|
Here are some project suggestions for your old comupter: https://kmandla.wordpress.com/2007/0...-old-computer/
|
Well, my first advice would be forget kde and gnome.
I was recently playing around with a laptop w/384M of ram and 1.2 Gh cpu and it was definitely usable so you're not wasting your time. I always use fluxbox btw. |
I've installed it with XFCE, got no luck trying to start X. This is what I've got http://pastebin.com/zWVpmEQE
And thanks for the suggestions but none of them seem to be very useful :/ I was thinking about trying something like Arch or ArchBang. |
We can give more targeted/relevant advice if you identify the hardware specs of the PC for us. :)
|
Ok, give me a second
EDIT: here http://pastebin.com/K3XiVsu6 |
Your questions are confusing:
Quote:
Or am I completely misunderstanding your questions? :) |
Device node was not created:
Code:
(EE) open /dev/dri/card0: No such file or directory Code:
[ 65.151] (--) PCI:*(0:1:0:0) 1039:6325:1039:6325 rev 0, Mem @ 0xc0000000/134217728, 0xcfee0000/131072, I/O @ 0x0000bc00/128 Code:
$ grep 6325 /usr/share/pci.ids |
I was just seeing if I could revive this ancient machine. The plan was to use it just to surf the web but I think it will be a horrible experience. To be honest, it is just curiosity, I don't think this machine can be used for something really useful (because I have other computers).
|
Quote:
Code:
xwmconfig Then issue this command: Code:
startx |
inxi :: a full featured system information script
http://code.google.com/p/inxi/wiki/Installation Code:
$ inxi -Fxz Quote:
|
I can't start X and I am sort of a Linux noob still so I have no idea what to do.
|
Quote:
|
To use graphics acceleration, regular user need to be a member of 'video' group. To check it just run:
Code:
id Code:
usermod -a -G video username |
Quote:
My bet is at an epic final, ... finally. Something like: "Finally, it WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOORKS!" In the mean time, you'll enjoy the googling in the text mode links... :hattip: PS. Hint: There is no video hardware acceleration for you, and, lot of fun, your X.org SiS video driver is technically unmaintained for years... |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Member Response
Hi,
Sadly, it looks like the OP will have issues with the old SiS driver for his video. Support for this legacy SiS hardware driver has been dropped. Maybe revert to earlier versions of Slackware to get his OLD hardware functional. |
Quote:
It would be helpful to know what the OP installed. Did he/she just install XFCE? |
I've installed everything, just dropped KDE and a few other packages. Of course I've installed Xorg.
|
Quote:
|
Greetz
This might be a good place and time, since we have some people new to Slackware, to point out a basic fact and a difference about Slackware. Basic Fact - Unlike Windows, installing an application or lots of applications in Linux does not stack up and contribute to so-called "bloat" other than hard drive space. Unless you run it, it essentially doesn't exist. This is one reason why Linux doesn't slow to a crawl over time. So there is no penalty, other than hard drive space to doing the recommended Full Install. Slackware Difference - Unless one installs some 3rd party device, by default Slackware Pkgtool of itself does not attempt to resolve dependencies, leaving that job to a human admin. Many people find this time consuming and unnecessary ... that is until they consider the time it takes to recover a system broken by dependency bots. In Slackware, if you fail to meet a dependency the worst that can happen is that one app will fail to run. The system remains intact. Fix that dependency, and it will join the others and happily run. Leave it for another time and never get around to it? No problem. It just still won't run but nothing else is at risk. For many the time spent resolving ones' own dependencies is well worth the time saved in troubleshooting since the only changes were made by you, so easily discovered as opposed to trying to follow the tentacles of dependency resolving bots which often install and remove packages far afield from the app one is trying to install. As for older hardware while it should handle newer kernels and systems just fine, since only what is needed will actually be used, there may be some benefit (and little loss) in using older versions, probably most notable in boot times, but having little effect once up and running. For OP, either XFCE or Fluxbox should work nicely. Fluxbox is lighter but does have a little less to offer the novice. With Slackware it is easy to try both by virtue of booting to commandline. One can launch either directly or through a login/display manager like GDM or KDM. KDM has an advantage of having a menuitem and ability to easily drop back to console. Best wishes and welcome to Slackware and LQ. |
It is not the first time I install Slackware without doing a full installation. The problem has nothing to do with it, and I think I will try an older version. Maybe 13.37?
|
Decided what I am going to do: set up the machine as a server to store my clonezilla's backups :)
|
For what it's worth, I am serving both a web log and Mediagoblin from a very similarly powered machine:
Code:
saul@farnsworth:~# head /proc/cpuinfo |
How did you set up the weblog? I've never set a server before
|
Quote:
The idea of a blog compiler is that you set up your theme and edit your entries using your favorite text editor, then you run the compiler to generate a formatted and static HTML blog. Your server then only has to provide the static webpages of your blog -- thus even a puny computer can handle thousands of visitors. One of the disadvantages of blog compilers is that comments from visitors do not get added until you regenerate the site. If this is not acceptable then you would need to investigate more resource hungry solutions such as Wordpress. Regardless what blogging software you use, you will need to provide a way for people to find your site. You might want to start by using a service such as No-IP or DynDNS, especially if your ISP is assigning you a dynamic IP address. Another simple solution is offered by Pagekite. These outfits all offer free domain name services as long as you are willing to accept a URL that is in their subdomain (for example, http://yourname.pagekite.me). Otherwise you will have to purchase a domain name. As for myself, I purchased my domain name registration from NearlyFreeSpeech.Net and use their API to update my DNS. This only costs me about $10 per year. |
I recently upgraded my old laptop, which has similar specs as yours, and I had similar troubles with it: X took ages to start and was practically unusable, regardless of the window manager or desktop environment I chose. However, during the holidays I finally found a solution that may help you, too.
The problem was that X was running without hardware acceleration in framebuffer mode, and didn't detect hardware capabilities correctly. It was using only 1 MB of VideoRam although my hardware supports 8 MB of VideoRam. I was able to solve this like so: X.org 1. Create an /etc/X11/xorg.conf. You can use the command xorgsetup (as root) to generate one for you. On modern hardware you don't need this, as X.org detects your hardware and in most cases loads the appropriate drivers and modules. But with some ancient hardware, such as your SiS graphics adapter, this fails at times. 2. Add a line for HorizSync in section "Monitor" (something like 30-50 depending on your display). 3. Add a line for VideoRam in section "Device". For my old laptop I added: Code:
VideoRam 8192 If there is a driver for your video hardware, the above might boost your laptop, too. ;) Next is a tip for a relatively rich, responsive and good-looking working environment on older hardware. Fvwm-Nightshade I found Fvwm-Nightshade quite good. It has a few minor bugs, as it is still a young project, but it provides a richer (== more end-user friendly) environment than Fluxbox and takes much less resources than Xfce. That latter would run quite well as such, too, but with opening a few applications I quickly reached the limit of the RAM of that computer. FNS uses about 100 MB less than Xfce, and without any applications running stays well below 100 MB. It is fast and user-friendly, and, to me, it looks good, too. Also, most of the required software is part of stock Slackware, and the rest is available from SlackBuilds.org. For my old laptop it's now my preferred working environment. Maybe you want to give it a try after your you have X running with support for your hardware. gargamel |
All times are GMT -5. The time now is 07:01 AM. |