Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
October 15, 2018, 04:40:23 PM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
9865 Posts in 306 Topics by 300 Members
Latest Member: IsidraStan
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 4 ... 18
16  Damn Small Linux / USB booting / Re: making a bootable DSL usb pen drive. on: February 05, 2018, 09:42:08 PM
First stop would be the wiki  (http://www.damnsmalllinux.org/wiki/installing_to_a_usb_flash_drive.html). Method II  (http://www.damnsmalllinux.org/wiki/install_to_usb_from_within_linux.html#Method_II:_Current_ISO_.2B_Syslinux) might be the simplest for you. EDIT: or method I. Also, you don't really need to go through all the reformatting/repartitioning stuff if you already have a suitably partitioned/formatted drive without anything on the target partition.
17  Damn Small Linux / HD Install / Re: Disk Write Error - Browser Crashes/Steam stops downloading on: January 28, 2018, 10:04:26 PM
It could just be that something went wrong during the partitioning/reformatting. To check the health of the HDD, find a program to read the SMART data, that will show counts of errors due to hardware issues.

P.S. Given that this isn't DSL related, it would have been better posted in the "Water Cooler" section.
18  Damn Small Linux / HD Install / Re: Please install HDD instructions from one device to another. on: December 23, 2017, 09:07:47 PM
Yes that should work with DSL. The only thing to consider is changing the boot settings (http://damnsmalllinux.org/wiki/cheat_codes.html) on the "kernel" line in /boot/grub/menu.lst if the destination hardware requires some particular boot commands. Besides that, just install and swap over the HDD. Job done.

Another option would be to boot DSL from USB and install from that (assuming the computer has USB).

EDIT: Also best run xsetup when you first boot on the destination computer. eg. by typing "e" at the grub boot screen and editing the kernel line to add the "xsetup" boot command.
19  Damn Small Linux / Other Help Topics / Re: Trouble installing gddrescue on DSL 4.4.10 on: December 22, 2017, 09:20:56 PM
I think you'd simply have to get lucky for that guide to work. The latest "Stable" debian release is so far ahead of Debian Woody now that I doubt much of the software, compiled as it is for a much later Linux kernel, would be able to run on DSL.

You could try packages made for older Debian versions than the current stable release, these used to be easier to find when the web interface to the Debian package archive  (http://archive.debian.net/) was up. I think you'd be better off just compiling it from source though. Software with just a command-line interface often compiles without too many dependancy issues on DSL, it's the GUI software where things tend to get difficult/impossible. It's been quite a while since I even bothered with the Debian packages.
20  Damn Small Linux / Other Help Topics / Re: Trouble installing gddrescue on DSL 4.4.10 on: December 20, 2017, 09:13:23 PM
If you can't get the debian woody package to work, I suggest compiling from the source code. This will provide a much more current version of the software anyway. See the guide to creating .tar.gz MyDSL extensions on the DSL Wiki for a guide to compiling in DSL.
21  Damn Small Linux / Laptops / Re: Ancient Dell E1705 on: December 20, 2017, 08:53:15 PM
DSL isn't fully Debian compatible to the extent that it can be completely upgraded using apt-get. Because the kernel upgrade would be to a new major release, it would break software that was specifically compiled for DSL and the 2.4.x kernel. I think there were some threads about this in the old forums.
22  Damn Small Linux / Laptops / Re: Ancient Dell E1705 on: December 19, 2017, 09:34:12 PM
The b43 drivers for linux support your wifi chipset, but they were only made for the Linux V. 2.6 kernel  (http://web.archive.org/web/20100824011022/http://bcm43xx.berlios.de:80/?go=devices). DSL-N Uses a V. 2.6 kernel, though I don't know whether it is above the V. 2.6.20.6 minimum or not.

Web searches bring up reference to an official kernel V. 2.4 linux driver released by broadcom as a binary. I'll leave you to find where that can be downloaded, assuming it's still around somewhere.

There's also the "ndiswrapper" approach, which is something I've thankfully never had to resort to myself.

For copying and pasting, highlight the text to copy, then press the middle mouse button to paste. If you only have two mouse buttons, press them both at once.
23  Damn Small Linux / Laptops / Re: Ancient Dell E1705 on: December 17, 2017, 09:52:38 PM
Does the wireless adapter show when you type the "iwconfig" command in a terminal window? What does it say about it in the output of the "lspci" command, or in the "PCI" tab of the "SYSTEM > System Stats" application?

You might want to check how you cope with the web browsers available in DSL before commiting. Firefox V. 2 has become very hard to use with many sites due to the "aging" of its HTTPS support, which coincides with the recent huge uptake of forced HTTPS on websites. I've long been meaning to look into compiling a recent Firefox ESR release for DSL, which I think might be just about possible, but I've got nowhere near the time lately.
24  Damn Small Linux / Other Help Topics / Re: Old Windows System, DSL, and a Printer on: December 05, 2017, 09:51:19 PM
Hello,

I just checked and there are no printer drivers for your printer included with DSL. However there is support included with the HPLIP library  (http://web.archive.org/web/20081015065410/http://hplipopensource.com:80/hplip-web/models/deskjet/deskjet_d4200_series.html) which is available in the MyDSL respository (in the "testing" section). You'll have to do some research on the DSL Wiki to learn how to set that up.

That said, I don't know whether the QEMU environment that DSL runs on within Windows is set up to support passing through USB devices. In any case it will be another matter to confuse the set-up process.

Overall I wouldn't recommend running "DSL Embedded" just for this printer. It still wouldn't allow you to print from Windows applications, so you'd have to save everything you wanted to print, then start up DSL in the virtual machine and open it in there for printing. At the end of the day, running a printer from 2007 on Windows 98 just isn't guaranteed, and in this case I think you'd be far better off finding another printer.

If you don't want to use a very old printer, one option to look at is Postscript printers. These can all communicate over a standard protocol, so you should be able to set up Windows with a generic driver that will work (you can certainly set up DSL that way). The trouble is that postscript printers are generally all "high-end" laser printers, but businesses often need to clear out old printers so there are often some very cheap, or even free, postscript printers floating around Ebay and classifieds websites. Most will have a small screen and keypad on them, so you can perform the "maintenance" operations without any special administration software on the PC.
25  Damn Small Linux / DSL Tips and Tricks / Re: New to DSL need guidance on: November 30, 2017, 08:54:53 PM
I haven't tried it, but DSLcore (http://distro.ibiblio.org/damnsmall/dslcore/) may be what you're looking for. I believe it was the early steps towards what became the separate TinyCore Linux (http://www.tinycorelinux.net) project.

The MyDSL Extensions are also on the DSL download sites (http://distro.ibiblio.org/damnsmall/mydsl/). There is also a respository browser program in DSL, though I don't know if it's included with DSLcore. Extensions can be loaded from the command line with the "mydsl-load" command.

You can also install packages made for for Debian Woody. Though if you want newer software, you'll have to compile it yourself. The compile.uci extension is a good start to setting up a compiling enviroment in DSL. Check that any software that you try to compile is compatible with the V. 2.4.x kernel used in DSL.
26  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.
27  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.
28  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.
29  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.
30  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:

Code:
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:

Code:
SOURCE="$1"

With this:

Code:
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="$1"
  to
  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".
Pages: 1 [2] 3 4 ... 18
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines
Mercury design by Bloc