Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
November 26, 2014, 06:36:15 AM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
297841 Posts in 294159 Topics by 213 Members
Latest Member: Raffles
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 ... 5 6 [7] 8 9 ... 11
91  Damn Small Linux / HD Install / Re: looking for a solution: installalling DSL persistently on simple computer on: August 06, 2013, 10:06:05 AM
"j" will probably be a LILO error code, you'll have to look at the LILO documentation to work out what error it is. You could always try GRUB, it is more commonly used with DSL. You should be able to do this from the command line as well as by re-running the script.

In fact the script I originally referred to is at the link in the DSL menu under "Apps>Tools" with the name "USB-HDD Pendrive Install", this may do a HDD-Install to the USB stick. Again I can't help you much further than this bacause I haven't done a USB install myself.
92  Damn Small Linux / Other Help Topics / Re: how3 boot to cli, then continue to x on: August 05, 2013, 06:40:30 AM
You can use the boot code "2" as described in the relvant page on the wiki (http://www.damnsmalllinux.org/wiki/cheat_codes.html).

Yes "startx" will run the GUI.

What model Android device are you using? It would be interesting to know how you get on.
93  Damn Small Linux / Laptops / Re: DSL on a ThinkPad A20m, how to add USB support and suspend/resume? on: August 05, 2013, 06:35:16 AM
I don't know of any way to use suspend or resume with the DSL GUI. This page (http://acpi.sourceforge.net/documentation/sleep.html) describes commands to trigger different sleep options (note that DSL uses the 2.4 kernel, so options "s3" and "s4" won't work). I haven't tried the commands myself, but I think I'll give them a go on my ThinkPad R31 tonight. If "s1" works for you, then you could make a one line script with the command and place a link to it on the desktop.

Actually, this page (http://dag.wieers.com/howto/thinkpad/a20m/) indicates that ACPI suspend can be triggered with the "fn-F4" keyboard combination. That doesn't work on my ThinkPad though.

As for USB, the above page indicates that it works, and they used the 2.4 kernel. Thinkwiki usually has some good information and there is a page on the A20m (http://www.thinkwiki.org/wiki/Category:A20m), but it doesn't have the USB chipset anywhere. To find this out, open "System>System Specs" in the DSL menu and click on the "pci" tab, then read off the text after "USB Controller:". You can also use the command "lspci" in the terminal. With that info, you can look up what Linux support there is for it in the 2.4 kernel.

Also, what are you using to test the USB? Some USB devices aren't supported by DSL.
94  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: August 04, 2013, 02:21:12 AM
That minimal console is the kernel on its own. Most of what makes Linux is additional software that is loaded by the kernel and your kernel can't find its files to load, so all it can give you is the basic system of built-in tools used for initial loading.

In relation to the bootloader, this means that GRUB has loaded the kernel and killed itself (that's a good thing, I coudn't think of another way to put it). The problem is that the commands passed to the kernel by GRUB (reading from the "kernel" line in menu.lst, hence why I've been talking about it so much) are not being properly understood or executed thereafter. In other words the kernel can't find its files (which are in "/dsl") based on the instructions you are giving it in the "kernel" line of menu.lst.

I can think of three potential causes for this in your case:
1. Your commands in the "kernel" line are incorrect.
2. The DSL kernel can't load its files from inside a sub-directory on a partition (your "/dsl" folder).
3. The kernel can't read data on the sda2 partition (eg. due to hardware incompatibility, data corruption or use of an unsupported file system).

Unless we are both missing something major and specific to your circumstance, then the kernel lines suggested by the Wiki, "james c" and myself should be correct, which makes no. 1 less likely.

If you can boot DSL from a CD etc. (with the "sata" boot code) and read the "/dsl" folder of the sda2 partition, then it is less likely that cause no. 3 is the problem. However it could perhaps be a problem that occours only at the early boot process.

Therefore I'm afraid that cause no. 2 seems rather likely. It would be worth doing some in-depth searching with Google for people who have tried booting the 2.4 kernel in a sub-directory of a partition, in case it was a known problem that was fixed in later kernels (such as the one used by Puppy).
95  Damn Small Linux / HD Install / Re: looking for a solution: installalling DSL persistently on simple computer on: August 04, 2013, 01:41:09 AM
Much of your first post indicated that the issue you have is with RAM running out due to the size of "/ramdisk". The anwser you are looking for (where the files from /ramdisk are stored on permanent storage media (eg. your USB stick) like on a traditional OS installation) is what is called in DSL a "HDD Install" onto a USB Memory Stick (look at the Wiki for more details).

As I said before, I haven't done this before, but "USB-HDD Pendrive Install" in the DSL menu may do what you want (if not, I am almost certain there is a way, however I don't have any experience in the matter).

If you cannot get a HDD Install to work on USB, remaining options are using a swap partition on the USB stick so that you won't run out of RAM, and setting up the DSL backup and restore systems for persistence. Otherwise you could do a HDD Install to the CF card that would almost certainly work if you used one large enough (and is still able to be used in other machines if you take it out of the case).

Now as for your web cam, that lsusb listing by no degree indicates that the device should be working. What you see is simply an identifier which the camera uses to tell your computer what it is and what driver to load for it. Having just checked, no driver for the device is included in DSL.

A quick Google of that identifier leads one to the first result (http://www.linux-hardware-guide.com/2013-05-18-microsoft-lifecam-vx-3000-webcam-usb-2-0) which indicates that the driver package for your web cam is "gspca". This is not in the my-dsl respository so you will need to either grab the modules listed on that page (the real file names will have ".o" on the end, eg. "gspca_sonixj.o") from the net (try to get ones made for the 2.4 kernel, they probably wont have been compiled for exactly the same kernel version as DSL, so they will complain when you will need to force them to load and they may not work). If you can't find them or get them to work, you will need to compile them yourself. I've posted notes on that process before in different circumstances (look at my past posts), but I've never compiled a USB driver in DSL before (at least, not that I can remember) so I don't know the details of enabling it in the "hotplug" USB management system that DSL uses. Source code compatible with DSL (not the latest version befause that isn't compatible) is at this link (http://mxhaard.free.fr/spca50x/Download/oldrelease/gspcav1-20071220.tar.gz)

With the driver loaded, and assuming the it is compatible with "gqcam", video will be available to the program at "/dev/video" and things will work (hopefully).
96  Damn Small Linux / HD Install / Re: Help with "Can't find KNOPPIX filesystem"? on: August 03, 2013, 12:22:25 AM
I've never used Loadlin with DSL, but I notice that the Wiki tutorial says that you should run it from a FAT32 partition while MS-DOS generally formats drives FAT16 by default (I've not used as late a version as 6.22 though, so this may be different in your case). I don't understand why the system would have a problem with FAT16, but that's what the Wiki says so its worth checking if you don't know.
97  Damn Small Linux / HD Install / Re: looking for a solution: installalling DSL persistently on simple computer on: August 03, 2013, 12:06:26 AM
I don't know all that much about installing to USB drives. If you can install to it in a similar way to a HDD Install, then that would be lightest on RAM and give you persistence. "USB-HDD Pendrive Install" in "Apps>Tools" in the DSL menu might do this, I don't know.

You say no HDD install possible, and one generally requires about 300MB, but you could buy a bigger CF card to replace the small one inside your machine, then do a HDD install to that. 1GB and 2GB ones are commonly available for relatively little money in stores and on Ebay.

Otherwise if you want to stay with your current set up, you could make a Linux swap partition on either your USB stick or your CF card (if there's enough free space) to act as extra (slower) RAM when you start to run out. There are plenty of guides on the net that describe that process.

As for keeping your files and settings, there are instructions on the wiki. (http://www.damnsmalllinux.org/wiki/persistence.html)

the command "apt-get" no longer works in DSL as the respository it uses no longer has files compatible with the version of Debian Linux that DSL is based on (Debian 3, "Woody"). Packages for Debian "Woody" are at the Debian Package Archive (http://archive.debian.net). You might be able to set apt-get to use that, but I don't know how. Those packages are no longer updated anyway, to use newer versions of software (which isn't in the My-DSL respository), you need to compile it yourself.
98  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: August 02, 2013, 10:50:58 PM
Just a thought (that should really have occoured before), what file system is on your sda2 partition? ext2 and ext3 should be supported by DSL, but some other ones aren't.

If you don't know, the best way to check (as fdisk lists all Linux file systems as type "Linux") is to boot Puppy, open a terminal and type "mount". One of the lines listed should start with "/dev/sda2" and further along that line, after the word "type" your file system should be stated.

EDIT: Whoops, seems I didn't ask that before because you already mentioned it was ext3. Oh well.
99  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: August 01, 2013, 07:56:57 AM
Presumably you've got your BIOS set to make SATA emulate IDE HDDs. I've run DSL on at least a couple of SATA systems (in one case to reformat a bunch of SATA HDDs, so I got used to the device names) and they always get named as "sd".
100  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 31, 2013, 09:34:25 AM
@james c
As he is using a SATA HDD, the device is named "sda", even in DSL.


The hash (#) on the kernel line won't stop the following commands, that only works at the beginning of a new line. You will have to delete the unneeded commands (you can always save a copy of your last menu.lst).

Your "KNOPPIX" cloop file and its directory are in the standard place, so with the kernel command "root=/dev/sda2/dsl", you shouldn't need "knoppix_dir=" and "knoppix_name=". That's assuming DSL doesn't mind running in your "dsl" directory.

You would have got the "ide1" command from the DSL WIki Boot Commands page. (http://www.damnsmalllinux.org/wiki/cheat_codes.html#Other_boot_labels)

What is the error you receive with the GRUB entry I suggested in my last post?
101  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 30, 2013, 07:24:13 AM
OK, let's try a different tact. Let me walk you through your menu.lst...

The first command to GRUB is "rootnoverify" which sets the active partition to (hd0,1). This is good.

Now we have that "ide1" thing which isn't a GRUB command (http://www.gnu.org/software/grub/manual/legacy/Commands.html#Commands). It is meant for a CD booting application and I don't know how to use it in this circumstance, but it likely has no relevance to your modern laptop and certainly won't mean anything to GRUB when you specify it as a command. Leave it out.

Now the kernel line which seems to have been the source of much confusion. "/dsl/linux24" is good, as long as "linux24" is a file located in the "/dsl" directory on the partition (normally it would be in a directory named "boot" or in "boot/isolinux/", but it makes no difference). Drop "fromhd=" as it relates to booting from a cd image which I don't believe you are trying to do. considering all the problems you're having, probably best to leave "home=" and "restore=" out for now too (they should state the drive sda2 though). Root should be back to "/dev/sda2/dsl", you could try the more standard "/dev/sda2", but this would probably create a lot of DSL folders in the "/" directory where you don't seem to want them. I don't know what "ro" does, it isn't in the list on the Wiki or in the default DSL "menu.lst", so I'd leave it out for now at least. "lang=us" is the default anyway, so this is a waste of bits and might as well be removed. "frugal", well yes, then "sata" which I told you to put there.

If you decide to use "/" as the root and therefore make the "root=" command read "root=/dev/sda2", add "knoppix_dir=dsl/KNOPPIX" to the kernel line so that Linux still knows where the KNOPPIX directory is.

The initrd line looks good now, as long as the file "minirt24.gz" is in the "/dsl" directory (again it would normally be in "/boot", or in this case case "/dsl/boot".

As I said before, I'm not 100% sure the "makeactive" command is required, but it won't hurt.

Of course there is nothing wrong with "boot", let's just hope it does.

Seeing as the contents of the "boot" directory are in the root "/dsl" directory, I do suppose that the KNOPPIX directory is inside /dsl with the file KNOPPIX inside it, eg. /dsl/KNOPPIX/KNOPPIX? Otherwise you will need to use the commands "knoppix_dir=" and "knoppix_name=" to tell it where the KNOPPIX file is (or better yet just put it where its meant to be).

How about opening a terminal when running Puppy and changing to the "/dsl" directory, then doing "ls -R" and posting the output? That would show how your DSL files are arranged in case it isn't the way DSL that expects.

EDIT- To clarify, this is the menu.lst entry I am suggesting (as long as the directory structure is mostly normal):
Code:
 title Damn Small Linux frugal in sda2 dir dsl
  rootnoverify (hd0,1)
  kernel /dsl/linux24 root=/dev/sda2/dsl frugal sata
  initrd /dsl/minirt24.gz
  makeactive
  boot

Simple, isn't it?
102  Damn Small Linux / Other Help Topics / Re: Tulip driver on: July 28, 2013, 01:20:11 PM
It looks like the drivers have loaded for your card (otherwise eth0 wouldn't be listed by ifconfig), they just aren't connecting to the net.

You can use the "pump" command to set up the network connection automatically using DHCP. I assume you are connecting to a router, in which case are you sure it can accept connections from new PCs and has DHCP enabled?
103  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 28, 2013, 01:34:58 AM
The "initrd" command shouldn't have "/dev/sda2" in the directory name. That is a command to GRUB which already knows what HDD you're talking about from the "rootnoverify" command, so you only need to tell it the directory and file name inside the drive.

I don't know about the "ide1" command. The wiki describes how to use it when booting from CD (where you have to type "dsl" before other startup commands), but I don't know how it applies to HDD booting. I'd put my money on it not being relevant to your modern VAIO anyway.

As I said before, I've never tried booting DSL inside a directory on the HDD. You should be able to get it to work, but you might find problems along the way (I'm not sure your current troubles are a result of that though).

How GRUB works:
I'm working off memory so this may be a bit general, but it should give you an idea.

When you boot a PC, the BIOS checks all the hardware and enables itself to behave as an interface between an Operating System and the PC hardware. In the days of DOS, this BIOS interface was used for all access to the HDD and FDD (this was before the days of CDs, so they wern't supported in this manner).

Nowadays Operating Systems ignore this and use their own driver software to access the hardware. However there is one stage where the BIOS is still important, in initial loading of the OS from the HDD. To do this the BIOS reads a specific area on the HDD named the Master Boot Record (MBR) where a tiny program is located which instructs the computer where and how to begin in loading the components of the OS.

The MBR is not a partition of the disk and it has no file system, it is simply a set area of the disk which is reserved for the tiny machine language loading program. The problem is that this reserved area is only 512 bytes. This is enough for a basic loader to start windows or DOS, but in multi boot systems, there is not enough room to store all the options and the interface of a multi-boot loader such as GRUB.

The solution is splitting the boot loader into stages. The first stage of GRUB is run from the MBR and simply runs a second stage that contains the code to enable the loading of the third stage which contains the menu and booting system. It is this third stage that we see and interact with using menu.lst.

All these stages are working in your case.

The "rootnoverify" (or "root") command tells GRUB which HDD/partition you want to work with (in case it is a different one to that on which GRUB resides). From there on, it is able to access the file system on that partition and load various components of the operating system. This process is specified through the commands in "menu.lst".

As a result, GRUB commands for OSs designed for booting using GRUB are standardised and should behave similarly in every case (unless they are incorrectly used of course). The exception to this is the commands after the initial directory specified in the "kernel" line (in your case "/dsl/linux24"). These are not used by GRUB, rather they are passed on to the kernel of the OS loaded. Therefore they are individual to each OS used and must use its system for specifying HDDs/partitions (Linux uses the "/dev" directory) as it does no know of the "rootnoverify" command passed to GRUB.

That was probably more detailed than you needed, but hopefully it clears up some of your uncertainty. The GRUB docs I linked to earlier have all the practical info such as the command descriptions for "menu.lst".
104  Damn Small Linux / Other Help Topics / Re: Tulip driver on: July 28, 2013, 12:17:09 AM
The Tulip driver is already in DSL in the directory "/lib/modules/2.4.31/kernel/drivers/net/tulip". It should be loaded automatically. Are you having trouble with your network card?

Modules may be loaded at the terminal using the "modprobe" command.
105  Damn Small Linux / Other Help Topics / Re: resolutions less than 640x480 on: July 27, 2013, 11:59:24 PM
I don't know how flexible it is, but the resolution commands are passed to TinyX as a command from the file "/home/dsl/.xserverrc". The "-screen" option selects the resolution.

 Here is the TinyX Man page: (http://www.x-oz.com/TinyX.1.html)
Pages: 1 ... 5 6 [7] 8 9 ... 11
Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc