Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
April 30, 2016, 08:50:59 PM

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

+  Damn Small Linux (DSL) Forums
|-+  Recent Posts
Pages: 1 2 3 [4] 5 6 ... 10
 on: January 16, 2016, 02:05:17 AM 
Started by jharris1993 - Last post by jharris1993
Sometimes when installing DSL - especially if the install has to be done on a different machine - the graphical display may encounter problems, the mouse may not work, etc. etc. etc.

So, how do you go about cleaning up this mess?


If you are still in the graphical display, type CTL-ALT-DEL, (the Windows "3-finger salute"  Grin ), to exit the graphical shell.

If you are at a "shell prompt" (which should look like dsl@tty1[dsl]$), you type in xsetup.sh

Once you do that, you will see a series of psudo-graphical dialogs that will ask you questions about your configuration:
*  Xvesa or Xfbdev?  ("normal" vesa graphics, or do you need Frame Buffer graphics?  If you get this wrong, your graphics might be garbage, or won't work)  You scroll up-or-down to select - if one doesn't work, go back and try the other.
*  USB mouse?  (yes or no)
*  (If no USB mouse) IMPS2 mouse? (is it a PS2 - round connector - mouse?)  (yes or no)
*  (If no USB or PS2 mouse) it will ask you about a serial mouse - I've never messed with this since my mouse is PS2.
*  Number of mouse buttons?  (2 or 3)
*  Screen Resolution?  (640x480, 800x600, 1024x768, etc.)  You arrow up-or-down to the one that matches.
*  Number of bits (color depth), (4, 8, 16, 32, etc.)  As before, you arrow up-or-down and hit Enter.
*  Keymap? (Here you arrow up-or-down to select the keymapping you want to use.)

After you do that, you can check your work by typingstartx to restart the graphical screen.

If everything works, including the mouse and it's buttons, you're golden!

If not, go back and try a different set of selections.

If you STILL can't get it to work, try asking a question here - include as much system and graphic card information as you can, and if anyone can help, you should hear back soon.

What say ye?

Jim (JR)

 on: January 16, 2016, 01:36:22 AM 
Started by jharris1993 - Last post by jharris1993

When using DSL in 640x480, Dillo opens up to a size that is too large for the available screen space.  Ergo, important controls like the address bar, or the window buttons, are missing.

Is there a way to constrain Dillo so that when it opens, it doesn't open larger than the available screen size?


Jim (JR)

 on: January 15, 2016, 10:26:27 PM 
Started by vturbo - Last post by CNK
Damn. Lost another post, I'm going to have to get into the habit of copying and pasting from a text editor.

Anyway, short grumpy version:

Probably a driver problem with your motherboard chipset. The fact that it boots to the desktop indicates that the USB drivers are working for the memory stick, so it's strange that they won't for the keyboard/mouse.

If keyboard & mouse are USB, then try PS/2 post if available. If using PS/2 ports, try USB.

Remember to run xsetup to configure the mouse to work.

Check the BIOS settings for any compatibility modes that have to do with the USB controller or mouse & keyboard support.

 on: January 14, 2016, 09:02:11 PM 
Started by vturbo - Last post by vturbo
hi huys, i have dSL on a usb stick which used to boot and work perfect on an old core2 duo base pc.

Since building new PC using an i7 i can boot to the welcome screen etc, but my keyboard and mouse stop working? everything works when i boot into windows 7 ok.

any ideas why my usb build doesnt work anymore on new PC?

cheers in advance

 on: January 04, 2016, 06:46:54 PM 
Started by jharris1993 - Last post by CNK
I get the impression that John isn't too warm on opening up the DSL project to a wider development team, but in any case there's nothing to stop a fork being created by another team or individual.

 on: January 04, 2016, 02:44:41 AM 
Started by jharris1993 - Last post by jharris1993

Excellent point.  And in retrospect, you are exactly right.  Unfortunately I was both hypothesizing, and not very lucid - it being WAY past bedtime when I wrote that.

In any event, I haven't had a chance to fuss with this yet.  However, hope springs eternal!

Re:  John not maintaining this-or-that:

First of all, I totally understand - I have a list of "I wanna do's" as long as my arm.  (Actually, both arms and both legs!  Cheesy )

Getting to things that you "want" to do often has to take a back seat to things that you "have" to do.  (Example:  John could have been a bachelor when this started, then got married, and THEN had a couple of kids to keep an eye on.)  Something like that - though enjoyable at times - really puts a crimp on the time you have to maintain a distribution.  Maybe he got a job that forces him to commute out-of-town for weeks on end?  Who knows?  He sure isn't telling.

One thing that could happen is for him to delegate maintenance responsibility to others who have both the experience AND the time to do the job.  Another option would be to share maintenance responsibilities with others.  There would have to be a way to coordinate activities so the maintainers aren't stepping all over each others shoes.  But if this is done it would serve to keep the DSL torch lit, and would provide an incentive to make things even better.

This is a big problem with any project that is a "one man band".  If that "one man" gets overwhelmed - or just develops a bad case of the fuckits, (which is absolutely undertstandable), things rapidly spiral out of control.

Just rambling. . . . .

What say ye?

Jim (JR)

 on: January 02, 2016, 10:29:38 PM 
Started by jharris1993 - Last post by CNK
The problem with your suggestion is that even when the file specified to Dillo on the command line isn't found, it still loads a blank window.

I think a better way to implement this feature would be to set an environment variable (something like $HELP) during the startup process which is checked using an "if" command in the .xinitrc script, in a similar manner to other parts of the script like selection of the desktop icons manager with $ICONS. SImilarly, I think that a boot line command to set $HELP on or off would be a good way to make the selection.

I'm afraid though that I am not a (the) DSL developer. The developer is registered on this forum as "John" (John Andrews), but has been inactive for the last few years since releasing the release candidates for V. 4.11 in 2012. There are some things I'd like to do myself, mainly compiling newer software releases as extensions for DSL, but I'm not willing to devote the time to it at the moment.

Submitting things would be a case of contacting John Andrews directly, but as I say, his inactivity indicates that it may be a long time before anything is done with your contribution. Another option is to package the changes as a MyDSL extension (see the Wiki for details), then submit it to the respository, or post here as an attachment if John isn't maintaining the MyDSL respositry either.

 on: January 01, 2016, 03:40:06 AM 
Started by jharris1993 - Last post by jharris1993
Just thought of something. . . . .

I don't think setting +/- x will prevent a local html file from being displayed in the browser.  Assuming that this is true, the fix would be to rename the file to have a leading dot.  Then the script will barf with a "file not found" type error.

Either way. . . .  It will be interesting to play with.

Jim (JR)

 on: January 01, 2016, 03:19:36 AM 
Started by jharris1993 - Last post by jharris1993
Thanks (and a Happy New Year!

Once I get a bit more familiar with DSL, (and if I can find a good spot on the Control Panel for this kind of tweak), I might take a shot at a "preference" to enable/disable this.  Though DSL is an excellent learning environment, I am sure that there are many users who blanch at the thought of editing their xinitrc!

One thought that might really work (at the functionality level - how to implement it in the control panel is another story!), is to add a call to another script in xinitrc.  The new script would work something like this

1.  Call the "getting_started" html page
2.  If it returns "not executable", just bail.  i.e. redirect stderr to /dev/null?

The preference toggle could work like this:

1.  Create two buttons - or a "flippy" button like the mounter has - and give it two states:
  (a)  Enabled
  (b)  Disabled

2.  Create a script that would do something like this:  (pardon the Windows coding style)

         message = "enable"
               chmod +x /usr/share/doc/dsl/getting_started.htm

         message = "disable"
               chmod -x /usr/share/doc/dsl/getting_started.html

Any thoughts on:
1.  How to implement this?
2.  (assuming I get it working) How to submit "upstream" (to you?) for inclusion in the next release?

You're right about one thing - Ubuntu/Mint/Fedora/Slackware/et.al. are two "damn" Grin complicated to try this kind of nonsense on without a whole lot more coding/scripting experience than I have.  (there's less to fight with, and less to "break")  There is (also) likely to be a less obnoxious "submit" method for patches/updates.

Any other development efforts going on now that DSL has risen like the Phoenix that it is?  I'd love to just hang out and soak up the skills.

Thanks again for your advice and encouragement!

Jim (JR)

p.s.  The "Preview" functionality on the board is broken - at least in Firefox.  Is there a place where I can submit bug reports against the forum site itself?

 on: December 31, 2015, 02:30:03 AM 
Started by linuxMigrant - Last post by jharris1993
I had run into much the same problem - and I spent much time pounding my head on my basement's cement floor trying to fix it - until I *FINALLY* figured out what the problem was:

The error message "ERROR: "/dev/cloop has no BIOS device name!" " translated from OS gibberish to human readable English is "The drive you're trying to install Grub on is not directly connected to the computer's motherboard somewhere.  Perhaps it's connected via a USB cable?"

I found the best way to get Grub to install was to take a computer and connect the hard drive directly to the computer's motherboard via either a direct IDE or SATA connection to the MoBo's (<-- geek-speak for "Motherboard"), internal connectors.  eSATA, FireWire, USB, etc. won't cut it since (in most cases) the device was not recognized as a bootable device at startup.

I did everything possible to "fix" Grub: Voodo, burning brown rice, sacrificing small rodents, threatening it with my gigantic wood-splitting maul, and so forth.  All to no avail.  It was only after I got a clue about what the error actually ment, and hooked the drive directly to the motherboard, that I had any success at all installing DSL on a hard drive.

Hope this helps someone.

Jim (JR)

Pages: 1 2 3 [4] 5 6 ... 10
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines
Mercury design by Bloc