Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
November 22, 2017, 10:16:19 PM

Login with username, password and session length
The new DSL forums are now open.
302360 Posts in 294244 Topics by 296 Members
Latest Member: Adisanut
Search:     Advanced search
* Home Help Search Login Register
Get The Official Damn Small Linux Book. Great VPS hosting provided by Tektonic

  Show Posts
Pages: [1] 2 3 ... 16
1  Damn Small Linux / HD Install / Re: Tried DSL's USB Boot guidelines, Rufus in DD, multibootusb, LILI. To no avail! on: November 13, 2017, 03:52:12 AM
The Grub bootloader itself should be installed to the boot partition on the HDD that the BIOS is set to boot from, it sounds like this is the one where you have Windows installed. It overwrites the Windows bootloader, which is why you need to include a command to start Windows in menu.lst (there should be plenty of guides regarding setting up Grub online, the Grub used with DSL is now called "Grub Legacy"). After starting up from the boot partition, Grub loads it's other files from whatever partition was specified when it was installed, which in this case should be the one with the rest of the DSL OS files in it.
2  Damn Small Linux / HD Install / Re: Tried DSL's USB Boot guidelines, Rufus in DD, multibootusb, LILI. To no avail! on: November 12, 2017, 11:03:28 PM
To install to an internal partition, follow the instructions for installing to USB  (http://damnsmalllinux.org/wiki/install_to_usb_from_within_linux.html#Method_III:_Using_GRUB_as_boot_loader), but using the partition on your target HDD instead of a USB drive.

You'll need to add an option for booting Windows to the menu.lst example, and also add the "sata" boot command to the "kernel" line of the DSL entry if you're using a SATA HDD. Change the "root=/dev/sda1" bit of the kernel line to match the partition you use as well.

If the partition is formatted as NTFS, you'll have to copy the files off it, reformat it to ext2 or ext3 for DSL, then copy them back.
3  Damn Small Linux / HD Install / Re: Tried DSL's USB Boot guidelines, Rufus in DD, multibootusb, LILI. To no avai on: November 12, 2017, 09:58:09 PM
That's typical of DSL not supporting the USB chipset used in your motherboard. It's a compatibility problem with your hardware, most likely because your hardware was made some years after the linux kernel that DSL is built upon was released.

If your external CD/DVD drive is USB, then it may suffer the same fate. Remaining options would be to use network booting, or to copy DSL to an internal hard disk partition and boot from it manually using Grub. Even then, you wouldn't be able to access USB devices within DSL.

DSL-N is based on a later kernel version than the main DSL and may have support for your USB chipset, so you could also try that.
4  Damn Small Linux / HD Install / Re: Tried DSL's USB Boot guidelines, Rufus in DD, multibootusb, LILI. To no avai on: November 12, 2017, 09:14:22 PM
What exactly goes wrong when you try to boot? Does the DSL splash screen display? Do you see the start of the startup sequence? Does it complain that it can't find the partition containing the operating system (or something that sounds similar)?

If you can burn a CD and boot from it, that may work better.
5  Damn Small Linux / DSL Tips and Tricks / Solutions to "Please mount optional dir and try again" Error on: October 22, 2017, 11:09:04 AM
Users of HDD installs, or who leave their computers running for very long periods, may have encountered error messages requesting them to "Please mount optional dir and try again" after attempting to load a MyDSL extension, or when sutting down their PC.

A simple solution to this problem is to replace the "/tmp/mydsl.map" file, which normally lists all loaded UCI extensions, with a template one containing 63 lines of the text "free". Such a file is attached with this post and can be set to automatically replace "/tmp/mydsl.map" on every boot by including a command such as the following in the "/opt/bootlocal.sh" script:

cp /home/dsl/mydsl.map.start /tmp/mydsl.map

The problem that the above partially solves is with the MyDSL UCI package system, which relies on unloading all loaded UCI packages on shutdown. The system fails to contend with packages loaded from a directory other than /home/dsl/, and also where packages have been renamed, moved, or were loacated on a filesystem that has been unmounted.

A better solution to the problem with packages loaded from outside "/home/dsl/" is to replace line 10 of "/etc/init.d/mountci", which reads:


With this:

SOURCE=`readlink -f "$1"`

A copy of "/etc/init.d/mountci" from DSL V. 4.4.10 with this modification already performed is also attached.

The replacement of "/tmp/mydsl.map" on each boot should still be performed to account for the other instances where the extensions system may get confused.

The following are some notes describing observations regarding the MyDSL UCI extension system, and more detail of the problem at hand:

*"Please mount optional dir and try again" prompt comes from "/etc/init.d/mountci", which is called from
 "/usr/local/bin/exitcheck.sh", which is called by "/usr/bin/dslexit" (exit
 window program).

*The error window is displayed by a call to the script "/usr/bin/popup.lua",
 but only if the $DISPLAY shell variable is of non-zero length.

*The call to "/etc/init.d/mountci" from "/usr/local/bin/exitcheck.sh" seems
 to be due to the presence of entries in the "/tmp/mydsl.map" file added when
 uci extensions are loaded.

*Removing, or creating an empty, "/tmp/mydsl.map" does not solve the problem.
 The UCI system works by looking line-by-line through "/tmp/mydsl.map" before
 loading an extension, and noting the first line number where it finds the word
 "free". It then mounts the .uci extension at the /dev/cloop device associated
 with that line number. So if line 5 was the first to read "free", the new
 extension would be mounted at "/dev/cloop5". It also replaces the "free" text
 on line 5 with the name of the extension loaded eg. "extension.uci".

*The problem with using only the extension name is that this means that the
 extension has to be in the current directory when the command to unmount the
 extension is executed. If it is in a different directory, as may happen when
 the "/usr/local/bin/exitcheck.sh" script attempts to unload all extensions on
 shutdown, the command will fail.
 -This has been solved by changing line 10 of "/etc/init.d/mountci" from:
  SOURCE=`readlink -f "$1"`
  Now the full directory path is always written to the "/tmp/mydsl.map", and
  "/usr/local/bin/exitcheck.sh" therefore succeeds in unmounting all loaded
  UCI extensions and marking their lines in "/tmp/mydsl.map" as "free".

*As no UCI extensions could be loaded when the OS restarts, it would be possible
 to add a command to copy a file with 63 "free" lines to "/tmp/mydsl.map" to
 "/opt/bootlocal.sh", therefore ensuring that everything starts afresh, even
 after a crash or power failure.

*A problem was noticed with "/usr/local/bin/exitcheck.sh" failing to edit the
 "/opt/.dfmext" file, this was (sort of) solved by doing a "sudo chmod a+rw /opt/.dfmext".
6  Damn Small Linux / Other Help Topics / Re: DSL as Host for VirtualBox?? on: October 19, 2017, 09:17:29 PM
I haven't tried it, but you will probably have some trouble getting VirtualBox installed. As far as I can see there's no MyDSL extension, and there was no package for Debian Woody (the version of Debian with which DSL is compatible).

This means that you'll have to build it from source, and the dependency list  (https://www.virtualbox.org/wiki/Linux%20build%20instructions) indicates that this will require first compiling a number of dependencies which are also not already available for DSL. QT 4 is likely to be difficult for one thing.

Whether it is possible or not will depend on whether one of the dependencies requires a later kernel than the 2.4.31 release used in DSL. If so, your only option might be to try to find an earlier version of VirtualBox that works with earlier releases of the problem dependency.
7  Damn Small Linux / User Feedback / Re: Thank you for keeping 32 bit alive on: October 13, 2017, 10:32:51 PM
I'm afraid DSL would be on life support at best, but indeed it isn't likely to be moving away from 32bit support for one thing.
8  DSL Not / DSL-N / Re: how to install siag on dsl-n on: September 15, 2017, 11:59:30 PM
There doesn't look to be an extension for it in the MyDSL respository. I'm not sure whether DSL-N was compatible with a version of Debian, but if so you can install the package for that Debian release from the Debian package archive. Otherwise you'll have to compile from the sorce code on the project's website (http://siag.nu/).
9  Damn Small Linux / USB booting / Re: I have DSL installed on a Fujitsu Stylistic 1200. How to reset firefox size on: September 01, 2017, 11:52:43 PM
Use the "-width" and "-height" command line parameters when you start firefox. eg. "firefox -width 640 -height 450".

You can add this in the "shellcommand" section of the options window for the desktop shortcut, after "!0!". For the link in the DSL menu, you can edit the file "/home/dsl/.jwmrc" and add the parameters after "/usr/local/bin/firefox" in there.
10  Damn Small Linux / Other Help Topics / Re: MyDSL Browser issue? on: August 26, 2017, 11:01:09 PM
In the DSL menu, select "Apps > Net > Download Mirror Selector", and enter one of the HTTP or FTP download links from the mirrors page  (http://damnsmalllinux.org/download.html).

Mine is set to: distro.ibiblio.org/damnsmall/
11  Damn Small Linux / Laptops / Re: no sound card and no drives on: July 26, 2017, 10:47:18 PM
The unused bit indicates that the driver isn't setting up the card, so unless something in the configuration has been messed up it looks like your chipset isn't compatible with the atheros (Madwifi) driver in DSL.

You could try DSL-N, which uses a 2.6 kernel. The software is a little less up to date than in the main DSL though. AntiX Linux is similar in some ways to DSL, you might be able to install emelfm2 in it using the package manager.
12  Non-DSL Topics / water cooler / Re: Lightweight Linux distros on: July 11, 2017, 12:03:10 AM
That's a great list, particularly given you've found the minimum requirements for every distro (I know how hard that can be for some). Actually it might have been handy if you'd linked to where the hardware requirements were stated for the distros, so they could be checked as time goes on.

There are a few there that I'll be looking into. All the big screenshot images on the main page did bog down my Pentium I rather badly though. Smiley

Some Distros from my LiveCD collection that I didn't notice there:

*Milax - min. Pent. I 128MB RAM (256MB for GUI)
*CDLinux - min. Pent. Pro, 64MB RAM
*TinyMe Linux - min. Pent. 1, 64MB RAM
*Plop Linux - min. 64MB RAM - Scratch built
*ttylinux - min. Pent. Pro 128MB RAM - Designed for terminal use only (no GUI)
*Feather Linux
*You might even mention FreeDOS, given that you have some other non-Linux distros there. Along with the official live CD, there is also one spin-off distro I know of (and have been meaning to try out): Svarog386  (http://svarog386.viste.fr). The Svarog86 version  (http://svarog86.sourceforge.net/) will even run on an 8086.

The system requirements are what I've written on my CDs, and are probably out of date for many of the distros as its been years since I made most of them.

I'll probably come back and post some more later.
13  Damn Small Linux / USB booting / Re: Cannot Access Internet on: June 19, 2017, 10:21:13 PM
Looking at the results of the "ifconfig" command in a terminal, as I mentioned above, is the way to identify names of the network interfaces detected on your computer.
14  Damn Small Linux / Laptops / Re: no sound card and no drives on: May 20, 2017, 12:43:40 AM
Here are the modules loaded on the PC I'm on in order to use the PCI WiFi card which uses an atheros chipset:
ath_pci                67484   1
ath_rate_sample         9736   0 [ath_pci]
wlan                  138904   1 [wlan_scan_sta ath_pci ath_rate_sample]
ath_hal               174608   1 [ath_pci ath_rate_sample]

The module files themselves are in "/lib/modules/2.4.31/net", and I believe they are part of the DSL 4.4.x installation. They load automatically for me.

The model of chipset is reported by lspci as:
Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

Perhaps that will be of some help if you need to load modules manually using modprobe. I don't know enough about alsa to be much help with the sound issue unfortunately.

Also, the WiFi card is identified as "ath0" instead of "wifi0" (which is left marked as "no wireless extensions.").
15  Damn Small Linux / Laptops / Re: no sound card and no drives on: April 25, 2017, 10:27:35 PM
That error means that the "cc" command, which should call the compiler, isn't being recognised. Did you run ./configure first? That might change the command used to "gcc" which is more usual. If it still insists on using the "cc" command, you could make a symlink called "cc" in /usr/bin, linking to gcc.
Pages: [1] 2 3 ... 16
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines
Mercury design by Bloc