Language Selection

English French German Italian Portuguese Spanish

DSL 2.1r1 on old Laptop

Filed under
Linux
Reviews
-s

The developers of Damn Small Linux have announced the availability of the first release candidate of version 2.1. My gentoo install is quite dated on my aging laptop, and due to speed and other certain hardware considerations (like a whiny harddrive after a couple hours of compiling), it isn't likely to be updated again. I decided to see if dsl could run on this ancient Dell laptop.

Damn Small Linux is a damn small linux distribution, literally. For those who don't know, it's a 50mb livecd that is also installable onto your harddrive or an usb key. It's a fully functional system consisting of an graphical interface featuring the fluxbox window manager and many useful applications and utilities/tools.

The Change log for 2.1r1 includes:
1. Improved SATA boot time support (see f3)
2. USB 2.0 boot time support fixed typo
3. Torsmo replaces asmem, wmcpuload, & wmnet to better support both window managers.
4. Ted replaces Flwriter
5. Updated xtdesk improved dragging when double click enabled.
6. New Icontool GUI controls many icon features.
7. Added missing tools section to jwm menu.

Well, the first test, to see if it would boot with only 80mb ram.

I needed to download and dd the bootfloppy img due to the fact that this laptop is so old, it doesn't support booting from the cdrom. How long before it's a fish sinker? Well, that may be inevitable, but it's not a fact today. My old laptop did in fact boot dsl on a p1 with only 80mb ram. However, (you knew there was a however, right?), the video/display wasn't very readable when just hitting enter at the boot prompt. I decided to reboot and try some of those fb modes the F2 options screen suggests is for laptops. Crossing my fingers I tried fb1024x768. When that didn't work, I tried fb800x600. That was the ticket. I was in. I was thrilled. I was comforted by the telltale "beep, beep" of the pcmcia network being activated (although it turned out to be short-lived). Then I was asked about which x server module to use, xvesa or xfbdev. I chose xfbdev and was asked about my lang and mouse. At the answering of those questions, X started and looked beautiful and my scroll ball mouse device worked too. Damn Small Linux scores again!

        

Fly in the ointment:

My old and commonly recognized pcmcia wireless network card (linksys wpc11 rev3 that uses orinoco) was incorrectly detected as some Bromax unsupported/unknown card. One can modprobe orinoco and it'd get loaded without error. Still no wlan or eth0 device was available. Also not correctly setup was my netgear FA411 wired pcmcia netcard (that uses 8390). However, we did have some luck with a 3Com/Megahertz 3CCFEM556B. So, whoops. One strike against. Have to, a laptop just isn't any fun if the wireless doesn't work. It's not just me, please see this post for confirmation.

Sound is another small issue. Actually it isn't. It wasn't correctly detected or setup, but in all fairness, it never is. It works fine in Linux, but I have to pass some specific options to the kernel for it to work. It's an old dell latitude XPIcd and I always have to use /sbin/modprobe sb io=0x230 irq=5 dma16=5. I can't tell you how long I spent finding that solution my first Linux install on this thing! Big Grin So, we'll give dsl the brownie point there.

But how would it perform on such a low resource system?

Well, overall, most excellent. Most light applications, like emelfm, Ted or xpaint opened within a few seconds. Dillo took about 9. Sylpheed required 3 or 4. However, mozilla took about 70 seconds to open and another 4 or 5 to render the dslos.com start page. It took about 6 second to render other sites at that point and there was a marked delay or unevenness (is that a word?) with scrolling. Of course, this isn't really a reflection on damn small, just an interesting note. Another thing, xmms was running at the time, which was requiring some cpu cycles to stream that default classical station it was playing. In addition, we're still running from the livecd at this point as well. I'd have to install Opera if I was going to install this onto my hard drive for sure, but given the fact that the pcmcia stuff is somewhat broken, I think I'll forgo the install and wait for the next rc.

        

Conclusion:

I found dsl to work rather well on this old laptop. Applications functioned well and looked quite nice, save mozilla. The video was great looking, the mouse device, cdrom and floppy worked fine of course, and the sound works with a bit of nudging. Some pcmcia cards work and some that should don't. The torsmo looked and worked great. I never did find that gui icontool in the menu (oh, ok, founnd it... hey, that's neato). In addition, I think there should be some kind of battery monitor. Once they sort out the pcmcia stuff, I'm sure it would perform much better from the harddrive.

        

Re: A wonderful review on DSL ?

atang1 wrote:

Its wonderful and tell tale DSL install.

Love your review of DSL.

Yeah, I'm going to soon replace gentoo with a binary distro and I think dsl will be the one.

Thanks for saying! I suffered with the "butterfly syndrome" as I hit submit, as I often do. I appreciate it. Smile

great review... UPDATE .....

UPDATE...

Added 128 mb of memory for a total of 160mb.

DSL now loads and works like a hot damm. Even found an older PCMCIA 3com network card and I had connectivity. Looks like the perfect distro for this laptop. Never would have beleived it if I hadn't tried it.

Nick

But tried it on a compaq presario 1200 with 32 meg mem. (k6 475 mhz processor)and it was next to useless. It booted up but took way too much time to get anything running.

Will try to upgrade the memory to 128m and try again

Nick

Great review but... Sorry for the duplicate...

DSL has lots of trouble on a compaq presario 1200 k6 475 with 32 m memory.

DSL boots up but just thrashes away continously. Got to find a 128 meg memory module to add or else its a doorstop.

nicsmr

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Programming/Development: C++, Go, Mozilla/Firefox and Python

  • Deliverable 1 : [✓]
    Seems okay, far better than the initial results. Although I should say, I deviated from what I thought I would need to write. First I assumed that I don’t have to write another boost::graph wrapper for KisPaintDevice, but I had to. That was one heck of an experience. In one of the last few posts, I ranted on Dmitry’s interpretation of the Graph, turns out we were on the same page but I understood his explanation the wrong way. I should put more attention to details from now on I guess. All the pixels are connected to each other, but they only have an edge between them if they are adjacent. If in center, the out degree would be 8, if in corners, 3 and if in edges, 5. There are some other cases too, but I will leave them for the moment. While writing the wrapper, I also got to know some of the cool features and techniques of C++, which I will be writing posts on as soon as I get some time, concepts, traits, avoiding virtual functions and what not. It is commendable that how boost approaches boost::astar_search, there is not a single virtual function, you don’t have to inherit anything (you can though for safety), just templates and traits, you are done.
  • Go Creeping In
    I’ve seen the inside of the Google and Amazon tech stacks. There are common threads that run through them and also, I bet, through most BigTechCos. Here and there down the stack is a lot of C++ and vestigial remnants from earlier days, Perl or PHP or whatever. Out in front of humans, of course, JS. But in between, there are oceans and oceans of Java; to a remarkable degree, it runs the Internet. Except for, here and there, you find a small but steadily increasing proportion of Go.
  • Stand by for FPR14 SPR1 chemspill
    Mozilla has shipped a fix for MFSA2019-18 in Firefox 67.0.3 and 60.7.1. This exploit has been detected in the wild, and while my analysis indicates it would require a PowerPC-specific attack to be exploitable in official TenFourFox builds (the Intel versions may be directly exploited, however), it could probably cause drive-by crashes and we should therefore ship an urgent fix as well. The chemspill is currently undergoing confidence tests and I'm shooting to release builds before the weekend. For builders, the only change in FPR14 SPR1 is the patch for bug 1544386, which I will be pushing to the repo just as soon as I have confirmed the fix causes no regressions.
  • PyPI Now Supports Two-Factor Login via WebAuthn
  • Understanding Python assignment
  • How to Publish Your Own Python Package to PyPI
  • PyCoder’s Weekly: Issue #373 (June 18, 2019)
  • EuroPython 2019: Community Discounts
  • EuroPython 2019: Inviting European Python Conference Organizers

today's howtos

All Linux, all the time: Supercomputers Top 500

Starting at the top, two IBM-built supercomputers, Summit and Sierra, at the Department of Energy's Oak Ridge National Laboratory (ORNL) in Tennessee and Lawrence Livermore National Laboratory in California, respectively to the bottom -- a Lenovo Xeon-powered box in China -- all of them run Linux. Linux supports more hardware architectures than any other operating system. In supercomputers, it supports both clusters, such as Summit and Sierra, the most common architecture, and Massively Parallel Processing (MPP), which is used by the number three computer Sunway TaihuLight. When it comes to high-performance computing (HPC), Intel dominates the TOP500 by providing processing power to 95.6% of all systems included on the list. That said, IBM's POWER powers the fastest supercomputers. One supercomputer works its high-speed magic with Arm processors: Sandia Labs' Astra, an HPE design, which uses over 130-thousand Cavium ThunderX2 cores. And, what do all these processors run? Linux, of course. . 133 systems of the Top 500 supercomputers are using either accelerator or co-processor setups. Of these most are using Nvidia GPUs. And, once more, it's Linux conducting the hardware in a symphony of speed. Read more

Red Hat and SUSE Leftovers

  • Are DevOps certifications valuable? 10 pros and cons
  • Kubernetes 1.15: Enabling the Workloads
    The last mile for any enterprise IT system is the application. In order to enable those applications to function properly, an entire ecosystem of services, APIs, databases and edge servers must exist. As Carl Sagan once said, “If you wish to make an apple pie from scratch, you must first invent the universe.” To create that IT universe, however, we must have control over its elements. In the Kubernetes universe, the individual solar systems and planets are now Operators, and the fundamental laws of that universe have solidified to the point where civilizations can grow and take root. Discarding the metaphor, we can see this in the introduction of Object Count Quota Support For Custom Resources. In English, this enables administrators to count and limit the number of Kubernetes resources across the broader ecosystem in a given cluster. This means services like Knative, Istio, and even Operators like the CrunchyData PostgreSQL Operator, the MongoDB Operator or the Redis Operator can be controlled via quota using the same mechanisms that standard Kubernetes resources have enjoyed for many releases. That’s great for developers, who can now be limited by certain expectations. It would not benefit the cluster for a bad bit of code to create 30 new PostgreSQL clusters because someone forgot to add a “;” at the end of a line. Call them “guardrails” that protect against unbounded object growth in your etcd database.
  • Red Hat named HPE’s Partner of the Year at HPE Discover 2019
    For more than 19 years, Red Hat has collaborated with HPE to develop, deliver and support trusted solutions that can create value and fuel transformation for customers. Our work together has grown over these nearly two decades and our solutions now include Linux, containers and telecommunications technologies, to name just a few. As a testament to our collaboration, HPE has named Red Hat the Technology Partner of the Year 2019 for Hybrid Cloud Solutions.
  • Demystifying Containers – Part II: Container Runtimes
    This series of blog posts and corresponding talks aims to provide you with a pragmatic view on containers from a historic perspective. Together we will discover modern cloud architectures layer by layer, which means we will start at the Linux Kernel level and end up at writing our own secure cloud native applications. Simple examples paired with the historic background will guide you from the beginning with a minimal Linux environment up to crafting secure containers, which fit perfectly into todays’ and futures’ orchestration world. In the end it should be much easier to understand how features within the Linux kernel, container tools, runtimes, software defined networks and orchestration software like Kubernetes are designed and how they work under the hood.
  • Edge > Core > Cloud: Transform the Way You Want
    For more than 25 years, SUSE has been very successful in delivering enterprise-grade Linux to our customers. And as IT infrastructure has shifted and evolved, so have we. For instance, we enabled and supported the move to software-defined data centers as virtualization and containerization technologies became more prevalent and data growth demanded a new approach.
  • SUSE OpenStack Cloud Technology Preview Takes Flight
    We are pleased to announce that as of today we are making a technology preview of a containerized version of SUSE OpenStack Cloud available that will demonstrate a future direction for our product. The lifecycle management for this technology preview is based on an upstream OpenStack project called Airship, which SUSE has been using and contributing to for some time. This follows our open / open policy of upstream first and community involvement.