Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
August 21, 2014, 02:04:09 PM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
297706 Posts in 294147 Topics by 206 Members
Latest Member: burak
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 10
91  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?
92  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?
93  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?
94  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".
95  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.
96  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)
97  Damn Small Linux / Other Help Topics / Re: chipset issues on: July 27, 2013, 01:44:35 AM
There's no log of supported hardware in DSL. The old forum archive might be the best source of info. I say give it a try yourself and report your success or lack thereof back here.

If the bug does prevent you from booting with GRUB, just use LILO as your bootloader and if the problem still persists, you might need to look at using an IDE HDD or a PCI SATA card.

Also, a SATA DVD drive will quite likely work because DSL uses a different booting system for the CD (err... assuming that system supports SATA drives at all).

Remember to use the "sata" startup command to enable SATA support in DSL.
98  Damn Small Linux / Other Help Topics / Re: chipset issues on: July 22, 2013, 07:13:47 AM
A bug in the 2.6 kernel might not mean a bug in 2.4. Looking in the bug report that the Wikipedia paragraph is based on, I don't see anyone talking about the bug occurring in anything other than the 2.6.17 kernel.

So there's no indication of whether it's a problem or not, but DSL is mainly aimed at earlier machines than those that use SATA anyway, hence the older kernel with smaller size and better support for older hardware. There is a lot of other new hardware which isn't supported in the 2.4 kernel.

DSL-N with its 2.6 kernel might be affected, but it will probably be replaced by the new DSL that John said he is working on.

Also, DSL comes with LILO as an alternative bootloader and presumably this doesn't suffer the same problem.
99  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 21, 2013, 01:34:25 AM
If you've got a SATA HDD, then you will likely need to put "sata" at the end of the "kernel" line (I do suggest you look at the table on the "cheatcodes" page in the Wiki). The drive will also be recognised as "sda", as mentioned before.

If that doesn't work, check the BIOS settings. I've rarely used DSL with SATA hardware (never tried to install), but it may be worth fiddling with the SATA settings such as IDE Emulation (maybe have a look through the archive of the old forum). Remember to take note of what settings you had to start with though.

The error basically means that GRUB is loading things happily, but the kernel can't find the drive/files for DSL. This might be because it is being told to look in the wrong place, it hasn't detected the drive (such as where SATA support isn't enabled), the filesystem is corrupt or there is a problem with the DSL files or directory structure.
100  Damn Small Linux / Other Help Topics / Re: how to install ez-ipupdate? on: July 19, 2013, 12:07:55 PM
That program isn't in the MyDSL respository so you will need to compile it from the source code.

This page has a guide to compiling programs: (http://www.damnsmalllinux.org/wiki/creating_a_compressed_extension_from_source.html)You don't need to make a tar.gz package for the MyDSL respository, but you are encouraged to so that you can help others who want the program.

That page doesn't tell you how to set up a compiling environment. An easy way to do this is to first install the following packages from the MyDSL repository:
  • gcc1-with-libs
  • gnu-utils
  • compile-3.3.5
101  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 19, 2013, 11:49:28 AM
Looking some more at the rest of your "kernel" command line, I think "initrd /dsl/minirt24.gz" should be on a line by itself beneath the "kernel" command. The ">" character after "frugal" shouldn't be there either.
Look here for an example: (http://www.damnsmalllinux.org/wiki/installing_grub.html#Booting_the_first_time) Don't know if "makeactive" is strictly required, but it wouldn't hurt.

You should have a look at this page as well: (http://www.damnsmalllinux.org/wiki/cheat_codes.html)
The commands there are meant to come after the "root=" command on the "kernel" line. A couple of the ones you have strangely aren't on the list (are you using the old version of DSL on this machine too?).
102  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 19, 2013, 11:16:28 AM
I suppose I was a bit ambiguous with the "root=" command as GRUB has its own "root" command (and similar "rootnoverify" command), in this case the equals sign makes all the difference.

The "kernel" command in GRUB passes everything after the location of the kernel, to the kernel once it is loaded. Therefore the "root=/dev/hda1" line would be interpreted by the DSL kernel with its "hd" disk designations, not by GRUB. Specifying "root=/dev/(hd0,1)" is asking the kernel to look for the item "(hd0,1)" in the "/dev" directory, which you can see for yourself is not there using a file manager. This, I suspect, it what the error "VFS: Cannot open root device "(hd0" or 00:00" indicates.

Section of the GRUB docs about the "kernel" command. (http://www.gnu.org/software/grub/manual/legacy/kernel.html#kernel)

As for the "sda" naming Vs "hda", this is related to the kernel versions. DSL uses "hd" to label IDE HDDs and "sd" to label SCSI, SATA, USB devices. Most modern linux distros (probably including Puppy) call all the drives "sd". Therefore if your desired partition is called "sda2" in Puppy, it will be "hda2" in DSL and hence your "root=" line after the "kernel" command would read "root=/dev/hda2". Also, I haven't tried this myself, but I figure if you want to run DSL in your "dsl" directory on hda2, then make the "root=" entry "root=/dev/hda2/dsl". Just to be clear, "rootnoverify" is a GRUB command, so keep the "(hd0,1)" format for it.

It looks like your VAIO is a few generations ahead of mine. As for the "boot" folder, I forgot you had a frugal install so the folders are a bit different. It doesn't matter.
103  Damn Small Linux / Laptops / Re: How to boot DSL using grub - frugal? on: July 18, 2013, 09:21:15 AM
Are you trying to boot from the HDD or the CDROM (i.e. what you were trying to do on your HP laptop?). If you are booting from the HDD then it looks like you have the wrong HDD/partition set as the "root" in menu.lst.

If you can boot from CD, look in all the HDD partitions in the /mnt directory and when you find one that has the Linux directories (bin, boot, opt, etc.) take note of it and enter it into menu.lst after "root=/dev/". If your HDD only has one partition, then it will probably be "hda1", so enter "root=/dev/hda1" into menu.lst.

If you can't boot the CD, tell me the model of your VAIO. I have an old one and could try booting DSL myself if it's a similar model.
104  Damn Small Linux / DSL Ideas and Suggestions / Re: Will DSL support ARM Architecture? on: July 16, 2013, 01:32:12 AM
Some time ago I was thinking about running DSL on an Android tablet I was given. I planned on using Qemu (http://wiki.qemu.org/) which can emulate X86 architecture on other systems. I never got around to the project, but the same approach should work (with quite a degree more ease) with a Raspberry Pi.

I did a quick search on Google and was surprised to find most people emulating a Raspberry PI on their PC using Qemu. Still, I found this forum topic on running Windows 95 (and even XP!) in the emulated environment:
http://www.911cd.net/forums//index.php?showtopic=24972

Of course it is a very inefficient solution, but using DSL I would expect pretty decent performance all the same (though the min. requirements are slightly higher than the first versions of Win 95).

As for a proper ARM version of DSL, I don't think there is anything in the works at the moment.
EDIT- I thought I remembered a topic like this coming up before: http://damnsmalllinux.org/forums/index.php?topic=13.0
105  Damn Small Linux / Other Help Topics / Re: DSL from router PXE - laptop is hanging for half a minute from time to time on: July 13, 2013, 12:26:27 AM
That's a weird problem. I've never seen anything like it on a computer that isn't scratching for resources. Still, a few things come to mind.

First, if you exit X and go to the terminal, does the problem still occur? If so, then ignore the next two suggestions. Otherwise, for where I talk about editing files, you'll need a HDD install. If running from CD or a "frugal" install, just do a "killall" command e.g. "killall torsmo" and see if it solves the problem (not quite as certain as disabling it at startup though).
--edit: Or just exit X, edit the files in the RAM drive using nano and then do "startx" to bring up X again. If you've run System Rescue CD, I'll assume you're happy with the Linux terminal.

That resource monitor (torsmo) at the top right of the desktop updates I think at the rate your problem it happening and it includes a network monitor (which has never worked on any system I've used with the net). The program can be disabled by commenting it out of the file "/home/dsl/.xinitrc". If that fixes things and you still want it running, you could try editing its config file "/home/dsl/.torsmorc" to disable just the network monitoring function.

You could also try changing the window manager to fluxbox and right clicking on a desktop icon and choosing to exit DFM from the menu (or to do on startup, edit "/home/dsl/.desktop" to read:
Code:
      wm: fluxbox
       icons: 0

If all this fails (not unlikely), it might be time for a bit of research. If your laptop is a rather unusual modern design, the chipset it uses might not have been fully supported in the DSL kernel (version 2.4.31, the other distros you tried use much later versions). You might have to hit Google hard to find out. If so, then there may be a driver package that you could compile for DSL and load as module/s on startup (however it may also exist and not support kernel 2.4).
Pages: 1 ... 5 6 [7] 8 9 10
Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc