Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
September 20, 2014, 02:00:58 AM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
297728 Posts in 294151 Topics by 232 Members
Latest Member: MLAC
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 ... 8 9 [10]
136  Damn Small Linux / Laptops / Re: Acer aspire one (a110) wlan don't work on: January 12, 2013, 12:10:29 AM
I take it you have tried the iwconfig GUI in the DSL menu under "Setup>Net Setup" and changed "device" from "eth0" to "ath0" before entering your network details. In that case, what error message did you get?

Many Atheros chipset devices are supported by drivers included in DSL, but if your one isn't detected, you may have to track down and configure another driver.
137  Damn Small Linux / User Feedback / Re: I am trying to create an image of an ultra light weight Linux that is deploy on: January 11, 2013, 11:56:40 PM
In anwser to your questions. First you need to decide whether you want a frugal or Hard Disk installation. I suggest you look at information on the DSL Wiki in order to work out which option you want.

Installation is simple. If the drive isn't already partitioned, do so using cfdisk, fdisk etc.. Then boot the DSL live CD and select "Install to Hard Drive" or one of the Frugal Install bootloader options (Grub is most popular) from Apps>Tools in the DSL menu. Now just follow the prompts to install DSL to the HDD of your choice.

However this will not get you far with the 486 laptop because DSL needs a minimum of 16MB RAM to run, and even then you would be limited to the terminal. For this purpose, I would suggest you use a distro called BasicLinux, which I myself use on a 486 laptop with 8MB RAM.

Using BasicLinux with a Pentium 4 though would be rather silly though as such a computer is capable of significantly more. So I suggest that the two computers should really run different distros to take advantage of their hardware.
138  Damn Small Linux / Laptops / Re: RT2070 USB Wireless dongle instalation on: December 25, 2012, 10:57:06 AM
Check the dependencies for RT2870USB, it might need a later version of "make", "gcc", etc. than the one you are using.
139  Damn Small Linux / Laptops / Re: Wireless not working with DLINK dongle on USB on: December 09, 2012, 05:29:02 AM
Looking here:
http://linux-wless.passys.nl/query_part.php?brandname=D-Link

Then at your lsusb listing, it appears that you have revision 2 of the DWA-140 device. That site shows that the driver for this is a version of the rt2870 driver designed for your card revision. To my knowledge, this driver is not included in DSL.

As a result, you will need to find a module (or group of modules) already compiled for the kernel used in DSL (2.4.31), or compile it yourself from the source code (if it is available). I described this process in greater detail here (ignore PCMCIA specific parts such as modifications to "/etc/pcmcia/config"):
http://damnsmalllinux.org/forums/index.php?topic=315.0

However, having attained the driver modules, you will have to configure them with HotPlug. I have no idea what this would involve as I have not installed a driver for a USB device in DSL. I understand that mainstream Linux distributions no longer use HotPlug, so keep this in mind when looking online for information.

also, if you have another wireless card about, it may be more suitable than the one you are trying.
140  Damn Small Linux / Other Help Topics / Re: RTL8180 / 8185 Drivers for Wireless PCMCIA card on: November 18, 2012, 03:24:39 AM
Your first port of call should be "linux-wless.passys.nl". This database lists the compatibility of a great number of cards with Linux and the drivers with which the working ones work. Or look at how puppy does it as described in the second last paragraph. Or seing as you already know the driver (when will I learn to read), just look it up directly and ignore what I say.

You now need to work out the Linux driver you need (should be some good hints at the above site) and what the module's file name is (with "_cs" on the end of the name for the PCMCIA version, and the ".o" extension). Now we need to have a peek in "/lib/modules/2.4.31/pcmcia" to find out if we already have the module in DSL. If it isn't there, use the find tool to search for the module anywhere in "/lib/modules" as I have a slight memory of some other modules hiding somewhere (I could well be wrong).

If the driver still can't be found (if it can, skip the paragraph after next), you need to really hit google and other file searching places for a module built for the 2.4.31 kernel. Try to find an old mainstream distribution to grab it from. Now chances are this will be a dead end (at least if my luck is anything to go by). Now if you can grab the source code of the driver from somewhere, you can compile it yourself, but this might be a bit of a leap for you (and I can't really help because I can never find the darn source code for my modules). Most likely you will find a module for another 2.4.x kernel version. This would probably work if we wern't using PCMCIA and just loading it with insmod and the -f parameter (or whatever the "force" switch was), however I've never been able to force the loading of modules in the PCMCIA system (if anyone out there knows, I'm all ears), hence it will stop loading with a message telling you to look at the kernel version.

The following will only work if you have a HDD install of DSL, if not then I don't have a clue what you would do. You should probably back up all the files you modify as well, just in case.

Now, if you did manage to navigate that minefield and end up with a module for the 2.4.31 kernel, we now need to set it up. Now this is where the time since I played around with this starts to tell and I can't guarantee that what I'm about to tell you isn't just the product of mixed and dying memories, but give it a try anyway. First copy the module to "/lib/modules/2.4.31/pcmcia" (unless it was already there). Now we want to open a terminal and do "cardctl id", from memory this should show you the identification info of your PCMCIA cards. Now we want to attack "/etc/pcmcia/config" with nano or another text editor run a root. Here, have a look at the top entries for devices and copy them, inserting the name of your module and classing it as "network". If your driver uses more than one module, look at the orinoco_cs driver for an example and check the web for the order they should be listed in (it might not matter, just my memory again). Now if we were building from scratch, you would have to create one of the "device" entries to identify the card based on the info you read with cardctl. But you said the card works with Puppy so you should be able to grab the relevent lines from the "/etc/pcmcia/config" file in there (I've never really used puppy, so I'm only assuming things are the same). So open that and search for some of the "version" info that came up with cardctl. When you find the relevent device entry, copy it somewhere, then load up the DSL one again and add it to that, remembering to check that the driver names are identical (otherwise just change it to the name of the driver you are using with DSL).

OK, now reboot the machine and see if the card is recognised, then open a terminal and execute ifconfig and iwconfig without parameters. If they show an entry other than "lo" (and "eth0" if the laptop has an ethernet port), then you have cause to try and connect to your wifi. If you have problems, open a terminal and use "lsmod" to show your loaded modules, if the module is there, then look up what name the card should have been given (eg. eth0 (which would be eth1 if you already had an ethernet port using eth0)) and try doing "ifconfig [name]", if it can't find the adapter then we have a compatibility problem with the driver. If the driver isn't listed by lsmod, then make sure the entries in "/etc/pcmcia/config" are correct and look for error messages at startup. Otherwise, the module/s could be failing to load due to an incompatibility, in this case you need to look at the boot logs.

Well I hope some of that was useful, good luck. If worst comes to worst, that $25 will easilly buy a known compatible PCMCIA wireless card 2nd hand off Ebay.
141  Damn Small Linux / Other Help Topics / Re: Firefox on DSL 4.11 on: September 29, 2012, 09:30:24 AM
64MB RAM is quite small for Firefox even though the processor should be fast enough. I think I can remember trying to load Firefox in DSL running with 32MB RAM on a Pentium 1 and had a similar experience with the CD access and slow loading time. I think that time I left it going while I did something else and by the time I came back it was loaded, so perhaps it might pay to give it some ridiculous amount of time.

Now I have 81MB RAM in that machine and a HDD install, Firefox loads in an almost bearable time but isn't really useable on a 120MHz Pentium 1.

However it could perhaps also be an issue with the disc you burned so it might be worth verifying that just in case.

As for installing newer versions of Firefox in DSL, check the archive of the old forum. I'm not sure if anyone got a post Firefox 2 version to work but if they did it would have been a struggle.
142  Damn Small Linux / DSL Ideas and Suggestions / Re: Your favorite lightweight apps? on: September 28, 2012, 05:19:44 AM
I would suggest that the next DSL include the XZ compression program as this format is becoming quite common nowadays. I compiled XZ-Utils a while ago (I might make an extension if get around to it) and it came to 3.4MB in total, though a lot of things could probably be left out to reduce this size.
143  MyDSL Extensions / System / Re: Current version: 4.4.10? on: September 28, 2012, 04:33:42 AM
Debian 3 "Woody" and kernel 2.4.31.
144  MyDSL Extensions / Games / Re: Games of Interest! on: September 18, 2012, 08:29:12 AM
Right, I emailed an extension to the address on the wiki (extensions2@damnsmalllinux.org).  I suppose this is still valid?
145  Damn Small Linux / Other Help Topics / Re: A problem with two KNOPPIX images on the HD on: August 26, 2012, 01:09:30 AM
I'm not familiar with Grub4Dos, however as it seems to use ordinary menu.lst commands for configuration, I would suggest that using the "root" command might solve your problem. This tells Grub which partition to operate from, otherwise it seems to guess the partition itself.

Try inserting "root (hd0,9)" (Grub counts from zero) as the first line under the title of the Feather Linux boot option in your menu.lst. Or if you can do temporary modifications to boot options at the Grub4Dos boot menu, edit it there for a quicker test.

eg.
Code:
title Feather Linux
root (hd0,9)
kernel /boot/linux24 root=/dev/hda10 <Options>
makeactive
boot
146  Damn Small Linux / Other Help Topics / Re: Laptop with broken screen how to connect external monitor ? on: August 18, 2012, 01:51:52 AM
Look through the BIOS settings for anything that refers to the display device, there should be a setting to tell the computer to use the external monitor as default. Then make sure the external monitor is plugged in when the laptop restarts.

Of course if you can't see enough to view the BIOS menus, you might need to try installing XFree86 and changing its configuration to use the external monitor.

Also, have you tried the laptop with other distros or Operating Systems? Or does Text mode display correctly? If the display problem is only in DSL then you might just want to try playing with settings in Xsetup.
147  MyDSL Extensions / Games / Re: Games of Interest! on: August 16, 2012, 09:30:54 AM
The only game I often play on DSL is the terminal based Tetris clone "tint", usually while waiting for some program nobody bothered to optimise for older hardware to go about its business. Of course tint isn't in the MyDSL respository so I had to compile it myself.
148  Damn Small Linux / Other Help Topics / Re: Internet connection on: August 08, 2012, 11:52:57 PM
So is this computer connected to the router wirelessly or with a cable?

If it's wireless, you want to use the iwconfig GUI, not netcard config.

However if the computer is connected to the router by an ethernet cable, then you should be able to use DHCP to automatically configure the settings. To do this, use the option named something like "Use DHCP Broadcast" towards the top of the netcard config window. When you select "yes", the troublesome boxes should be dimmed out and you can simply click apply at the bottom. This way your PC talks to the router to work out the settings itself.

If this doesn't work, find the settings of your other computer (which I assume is also connected through the same router and working) by opening a terminal and typing "ifconfig" in Linux or "ipconfig" in Windows and read off the IP address. Then type it into the IP box of the DSL PC but increase the value of the fourth number by one. eg. if it is "192.168.0.101" on your working PC, use "192.168.0.102" for the DSL machine.
Pages: 1 ... 8 9 [10]
Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc