Posts filed under ‘Puppy Linux’

Removing auto dhcp on startup for Puppy Linux

In Puppy Linux, when you select “Auto DHCP”, the interface will ask if you want to save the configuration. Unfortunately, one side effect or this is when you boot up and you are not near a network, your machine will hang until it times-out on DHCP (though you can press OK to bypass). How do you undo that auto dhcp on startup?

When you save configuration, the file is saved to a file name /etc/{interface}mode. The interface name you can get by running Puppy Network Setup. On my machine, the interface for my wireless is rausb0, so the interface file is /etc/rausb0mode. When you startup Puppy, it runs /etc/rc.network, which calls all of the /etc/*mode files.

To fix the problem, edit the script to remove the dhcp or delete it entirely. In my case, I just deleted the /etc/{interface}mode file.

May 29, 2007 at 7:40 am Leave a comment

Upgrading Puppy 2.15CE to 2.16

Puppy 2.16 has been release recently and I decided to upgrade from 2.15CE to 2.16. I backed up the pup_save file and then use Puppy 2.16’s universal installer to install the software onto the USB key. The upgrade did not work as expected since Puppy did not boot into X-Window as I expected to. I did encountered several problems:

  • The /etc/X11/rc.d/rc.modules were overwritten. I had thought that my changes were saved to my pup_save file, but apparently not. Fortunately, I had documented the changes in a blog. I just basically copy the settings back. In the future, I will save a copy of the rc.modules file.
  • My dev_215.sfs was removed. I downloaded dev_216.sfs in its place.
  • There are two drives on my desktop. I deleted the older one.
  • My Open Office is missing. I downloaded the new Open Office 2.2 sfs file.
  • SeaMonkey’s home page is the 2.15CE community page, which no longer exists. Fixing it was as simple as setting it to a new home page.

There is an additional step after you install the sfs files. You need to select menu->System->Bootmanager Configure. Click on the button to select the SFS file and move the two sfs file to the right. Reboot machine. Actually, the first time I tried this, it did not work. I unchecked the option to ignore the entry and manually move the files again and reboot. This time it works for some reason.

May 21, 2007 at 12:30 am Leave a comment

What does DotPet use as a signature

In Puppy 2.14 or later, you can register your DotPet Package. After registration, you can upgrade Puppy without overwriting your package. You can also uninstall the package. Recently, I created a DotPet for Ruby and Ruby documentation. I had named the two packages as Ruby-1.8.6-i486 and Ruby-1.8.6-doc-i486. Much to my surprise, when I installed the two packages, the second package overwrote the first.

I wondered what sort of signature Puppy was using as the DotPet signature. Examination of the dir2pet script indicated that the config file only logged whether to register the package or not, so I had guess that it had to be filename.

Expermientation indicated that the signature comes from the filename before the dash version number. So if the package is ruby-1.8.6-i486, the signature is ruby. The reason the doc install overwrite the package is because ruby-1.8.6-doc-i486 also resolve to a signature of ruby. To get a different signature, you need to add the “-doc” before the version number.

I rename the packages to “ruby-1.8.6-i486” and “ruby-doc-1.8.6-i486”, and it worked fine. When you create the ruby-doc, make sure that you enter “ruby” as the dependency.

May 6, 2007 at 5:46 pm Leave a comment

Installing Ruby on Rail in Puppy

Ruby on Rails is an open source web framework for developing web based, database driven application based on the Model-View-Controller model. At the minimum, the installation will consists of the following:

  • Ruby Programming Language
  • Ruby GEM library
  • Ruby on Rail framework
  • Ruby Database Driver
  • Database

The most common database is MySQL. However, compiling MySQL is tricky and the database has a rather large footprint to fit on an USB flash drive. Fortunately, Puppy comes with a Sqlite3, which we can use as the database.

Ruby on Rail has a built-in webserver call WeBrick. Optionally, we can install a standalone web server like Apache or Lighttpd.

The following are instruction for installing Ruby on Rails on Puppy Linux 2.14 with the minimal component needed to play around with Ruby on Rail.

  1. Before you start, make sure that you have the developer sfs installed. The Puppy developer SFS usually exists as a devx_xxx.sfs file where xxx is the version number of Puppy. You will need the developer SFS when you run gem.
  2. Install Ruby on Rails. I have create a dotpet to facilitate the install. All you need to do is download the Ruby DotPet file and open it from Puppy’s filemanager Rox. It will prompt you to install the package. Press Install.
  3. If you wish to install the interactive documentation, download the Ruby Doc file and open it from Rox. It will prompt you to install. Press Install.
  4. Download the Ruby GEM library. Download the latest tgz file into my-document. Untar the file by running the following command. I debated creating a DotPet for this but the tools weren’t able to record gem scripts, so we will download and run GEM:
    tar -xvf rubygems-0.9.2.tgz
  5. Once the file is extracted, we can run the setup file to install Ruby Gem.
    cd rubygems-0.9.2
    ruby setup.rb
  6. Use Ruby GEM to install Ruby on Rails. Note that you must have an internet connection open because Ruby GEM will connect to a server and download the software. If install fails, try again (I had to try twice).
    gem install rails --include-dependencies
  7. Use Ruby GEM to install the Sqlite3 driver sqlite3-ruby. Previous version of the driver required the SWIG package, but sqlite3-ruby 1.2.0 removed that dependency.
    gem install sqlite3-ruby
  8. You are prompt to select which gem to install. Select the latest GEM for your OS (in this case, it’s sqlite3-ruby 1.2.1).

Testing the Installation

To test if the framework is install properly, we need to create a simple program that exercise the entire framework.

  1. Open a terminal window and go to a directory. Enter the following command to create a Ruby project:
    rails smoketest
    This will create a directory call smoketest and a group of subdirectories.
  2. Next, we need to create a sqlite3 database and create a simple table in it.
    cd smoketest
    sqlite3 smoketest_development "create table books (isbn integer primary key not null, title varchar(25) not null);"
    This will create a database call smoketest_development and populated with a empty table books. Normally, we would have a development, test, and production database, but this is only a test so we will just create one.
  3. edit config/database.yml file. Change the adapter from “mysql” to “sqlite3”. This file specifies the development test and production database and the user account to connect.
  4. We’ll use Ruby to generate a scaffold. The scaffold generator creates a model “book” and map it directly to the database table “books”, it also generates a controller to manipulate the table, and a view to display the content of the table in a webpage.
    ruby script/generate scaffold Book RubyTest
  5. Start the Ruby Web Server by running the following command in a terminal.
    ruby script/server
    You should get a prompt that WEBrick is booting.
  6. The web server defaults to port 3000. We can connect to the server by hitting the following url:
    http://localhost:3000

    You should get the standard Ruby “Welcome aboard” page.
  7. If you can get to the Ruby server’s welcome aboard page, try hitting the test page:

    http://localhost:3000/ruby_test
  8. The screen should display the page for the table books. You can try to add a new book but clicking on the new book link.

March 17, 2007 at 3:49 pm 8 comments

Creating a Ruby DotPet in Puppy 2.14+

Puppy Linux 2.14 introduce a new package manager call dotpet, which replaces dotpup. Creating dotpet is mostly automated and is much easier than manually creating a dotpup. This article talks about creating a dotpet on Ruby. The instruction should also work with later version of Puppy.

Ruby is a interpreted programming language designed for programmers. We will do the following:

  1. Backup your pup_save.2fs file.
  2. Download the source code.
  3. Configure and compile the source code.
  4. Create a DotPet Package.
  5. Testing the package.
  6. Sharing your DotPet with others.

Backing up your pup_save.2fs file

The first thing you should do is to backup your pup_save.2fs file. The pup_save.2fs is a storage file that contains all of the changes you made. You need to back up this file because if you screw up, you can restore your changes. Many programs have a make install, but programs with make uninstall are as common as chicken tooth.

To backup the pup_save.2fs file, just make a copy of it and store it somewhere such as a CD-R. Remember to do this or you’ll be sorry!

Downloading the source code

You can get the latest Ruby language release from the Ruby Site. Download the latest stable version somewhere. I usually download it to a directory under /root. Make sure that you have enough space in your pup_save.2fs file to hold the download.

Ruby has its own package management system call GEM. I tried to create a DotPet for GEM, but the new2dir script isn’t really design to record GEM installation. It only managed to record one line.

Configuring and compiling Source Code

To compile the source code, you’ll need to set up the Puppy Linux development environment. This consists of copying a devx_214.sfs file to the same directory as your pup_save.2fs file and then restarting Puppy. The dev_214.sfs file will not work unless there is a pup_save file. When you install Puppy for the first time, there will be no pup_save file, so you won’t have the development environment until you reboot.

  1. Open a console.
  2. Change directory to the Ruby package.
  3. Untar the package:
    tar -xvf ruby-1.8.6.tar.gz
  4. Change into the directory created by the package.
    cd ruby-1.8.6
  5. Run configure to set up the makefile. The i486 parameter is so that the program will be build to a 486. While most people these day probably have a 686, you should still compile to a 486 if you plan to share your DotPet with others. Puppy Linux itself is built to a 486.
    ./configure --host=i486-pc-linux-gnu
    Note that there are two dashes in front of host. In earlier edition of Puppy, we would install the application in /root/my-applications because an upgrade of Puppy may wipe out our installs. DotPet avoid this problem by allowing you to register the package with Puppy so that this doesn’t happen (at least in theory any way).
  6. Compile Ruby by running
    make CFLAGS="-march=i486 -mtune=i686"
    The CFLAG are compiler flags passed to the C compiler. The above tells the compiler to compile to a 486 so that the program will work with anything 486 and above, while the i686 flag optimizes the binary for a 686, which most computer of today are based on. This option is the best of both worlds.

Creating a DotPet Package

Creating a DotPet is pretty easy. The package script records the files installed by make install. This is a one shot deal. Once make install installs all of the files, running new2dir make install a second time won’t record the files because they are already installed. This is why you should back up your pup_save file.

Though this isn’t in the Ruby readme file, Ruby really intalls into two packages: Ruby and Ruby Doc. Ruby is the programming language. Ruby doc is the interactive documentation (the doc you get when you type ri). We’ll need to create two different packages.

Creating Ruby DotPet

The Ruby DotPet contains the actual Ruby Language minus the Ruby documentation.

  1. Run the DotPet script:
    new2dir make install
  2. Step 1: You’re prompted to enter the package directory. Press Enter for the default option
  3. Step 2: You are asked what cpu the code was built to. Press enter to default to 486.
  4. Step 3: You are asked if you wish to create one or multiple packages. The multiple packages are for cases when you want to separate the package with the shared libraries. Ruby is fairly lean on its own, so just press Enter to accept the default of one package
  5. Step 4: Press Enter to record the make install.
  6. Finished: Press Enter to exit the new2dir script.
  7. Type the command: cd ..
  8. You’ll notice a ruby-1.8.6-i486 directory and a ruby-1.8.6-i486.files. The directory contains all of the install files and .files contains a list of the files. You can then convert the directory and files to a Dotpet by the following command:
    dir2pet ruby-1.8.6-i486
  9. The instruction asks if the name is in the correct format. It is, so press Enter.
  10. Step 1: the instruction ask if there will be a menu. Ruby is launched from the command line, so you type “no” and enter.
  11. Step 2: you are asked to enter a description. Enter “Ruby programming language”.
  12. You are given a list of packages in Pup_xxx file. I am not sure why we get this list, but I assume it is so you can see what packages are already in the system so you don’t build duplicate packages. Press enter to continue.
  13. You are given a list of packages in unleashed. I assume that this is so you can check if the package you are building is already in unleashed. Press enter since Ruby is not an unleashed package.
  14. You are asked about dependency list. Ruby is fairly independant, so press enter.
  15. Step 4: You are asked if you want to register with PETget. If you register with PETget, you can use the package manager to uninstall your package. If you upgrade your Puppy, it will known not to overwrite your files (in theory). Type “yes” and press enter.
  16. Step 5: you are informed that the dotpet is created. You should see a .pet file.

Creating Ruby Doc DotPet

The Ruby Doc contains the interactive documentation to Ruby. The DotPet tools documentation indicated there is an option to generate additional packages (ie: development, doc, etc). However, it also said that the script may not be reliable. The most reliable way is to just create it independently from ruby.

  1. Because the new2dir create the preprocessed files based on the name of the base directory, you need to rename the Ruby source directory. Otherwise, we’ll overwrite the previous package. In this case, we’ll rename the source directory to “-doc”. You need to do this before the version number because Puppy uses the name before the version number as the signature. If you type in “ruby-1.8.6-doc”, it will be shorten to “ruby”. If you install both packages, the second one will overwrite the first. You should use ruby-doc-1.8.6 instead of ruby-1.8.6-doc.
    mv ruby-1.8.6 ruby-doc-1.8.6
  2. Now you can run the new2dir script on the installdoc.
    new2dir make install-doc
  3. Step 1: You’re prompted to enter the package directory. Press Enter for the default option
  4. Step 2: You are asked what cpu the code was built to. Press enter to default to 486.
  5. Step 3: You are asked if you wish to create one or multiple packages. The multiple packages are for cases when you want to separate the package with the shared libraries. Ruby is fairly lean on its own, so just press Enter to accept the default of one package
  6. Step 4: Press Enter to record the make install-doc.
  7. Finished: Press Enter to exit the new2dir script. There is some sort of bad interaction between new2dir and make install-doc that cause it to go into an infinite loop. I had thought that the process was slow, but after a few days the script was not complete and I notice that ruby-doc-1.8.6-i486.files hasn’t been updated in a while. I would basically check the .files and if nothing has been updated for a couple of hours, break from the program using CTRL-C.
  8. Type the command: cd ..
  9. You’ll notice a ruby-doc-1.8.6-i486 directory and a ruby-doc-1.8.6-i486.files. The directory contains all of the install files and .files contains a list of the files. You can then convert the directory and files to a Dotpet by the following command:
    dir2pet ruby-doc-1.8.6-i486
  10. The instruction asks if the name is in the correct format. It is, so press Enter.
  11. Step 1: the instruction ask if there will be a menu. Ruby is launched from the command line, so you type “no” and enter.
  12. Step 2: you are asked to enter a description. Enter “Ruby Documentation”.
  13. You are given a list of packages in Pup_xxx file. Just as before, press enter to continue.
  14. You are given a list of packages in unleashed. Press enter since Ruby is not an unleashed package.
  15. You are asked about dependency list. Enter “ruby” and press enter.
  16. Step 4: You are asked if you want to register with PETget. Type “yes” and press enter.
  17. Step 5: you are informed that the dotpet is created. You should see a .pet file.

Testing the DotPet package

When you create your DotPet file, you will have install the package. To test it, you can install it again, test it, and then uninstall it.

  1. In a command line window, type “irb”. You’ll get a message that the command is not available.
  2. Launch Menu->Filesystem->Rox-Filer file manager
  3. Click on the ruby dotpet file that you created.
  4. Click on the install button.
  5. Press OK when install is complete.
  6. Launch terminal and type in irb. Ruby should start. If you type ri, it will not work because documentation is still not installed. Exit terminal.
  7. Click on the Install icon on your desktop. This brings up the package manager.
  8. Click on the PetGet package manager button.
  9. Click on the Install Package button (the large one). You should see a list of packages. On the right panel should be an entry for the package you just installed.
  10. Using Rox, click and install the Ruby-doc package.
  11. Open a  terminal window and type ri.  The command ri should now work.

Sharing your DotPet with others

Follow the instructions in this link to upload the package. In general, you need to use the ftp site to upload your package and then use messaging to inform the admin where to put your package.

Keep in mind that Puppy is a community release linux (as oppose to a Enterprise linux like Red Hat). Infrastructure support is limited and on a volunteer basis. The FTP server has been semi-unreliable so I had to try a few times to upload. The admin may take a bit to get back to you because they are volunteers with a life. Be patient!

I hope that this blog has been helpful and that you will contribute your dotPet.

March 17, 2007 at 3:05 pm Leave a comment

Creating a Ruby DotPup in Puppy Linux 2.13

Ruby is a programing language. Ruby does not come with Puppy. There is a DotPup for Ruby, but it is for version 1.8.3 and dates back in 2005. Before you start, you must have the development environment installed. To install the development environment for Puppy, download dev_xxx.sfs to your /mnt/home directory (where xxx is your Puppy version ex: dev_213.sfs).

  1. Download Ruby. The file will be in a gz format.
  2. Untar the filetar -xvf ruby-1.8.5.tar.gz
  3. Change directory into the new directory.
  4. edit the configure file, locate the line:ac_default_prefix=/usr/localtoac_default_prefix=/root/my-applications. This changes the install directory from the usual /usr/local to Puppy’s /root/my-applications.
  5. Execute config by typing ./configure, this generate several config files and makefile.
  6. Execute make by typing make. This compiles Ruby.
  7. Install Ruby by typing make install.
  8. Grab a list of files that was installed by:find /root -print | grep ruby > filelist
  9. Tar the files by:tar -cf dotpup.tar -T filelist
  10. compress the tar file:gzip dotpup.tar
  11. Create a readme.txt file. The file should describe where the software will install to.
  12. Create a dotpup.sh file (copied from the original puppy dotpup by Erik Veenstra). Make sure that you set the execution bit:#!/bin/sh# Installs Ruby to my-applications/binrox readme.txt

    PDIR=$(pwd)
    cd /
    tar xzf $PDIR/dotpup.tar.gz

    sleep 5 # Rox needs some time to open the readme.txt…

  13. Generate md5sum files for the 3 files.md5sum dotpop.sh readme.txt dotpup.tar.gz > md5sum.txt
  14. Create the Pup file using zip:zip ruby-1.8.5.pup md5sum.txt dotpop.sh readme.txt dotpup.tar.gz

Notes

  • The above DotPup does not include an uninstaller.
  • If you want to uninstall your package from the GetPup GUI, you have to create a uninstall script and register the install with GetPup.
  • Version 2.14 (which is not out at the moment) contains a new package management system call DotPet. DotPet comes with tools that automate  a lot of the process.

February 7, 2007 at 11:05 pm Leave a comment

Running Puppy Linux 2.14 on Averatec 2370

Puppy Linux is a live CD distro designed to be small, fast, and bootable from a removable device. I like the idea of a portable OS on a CD or a USB stick that can boot into another computer and leave no trace. I could lug a CD or USB stick instead of a computer. I decided to try installing Puppy Linux on my Averatec 2370 laptop. This is a relatively new machine, so installation may be difficult due to new hardware.

What works out of the box

  • Optical drive
  • Hard drive
  • USB ports
  • Sound

What doesn’t work out of the box but can be configured

  • Wireless
  • Fan
  • Power Management

What doesn’t work out of the box and still needs additonal software

  • Nvidia video – need to download video driver dotpup file

What doesn’t work period

  • 4-in-One SmartCard Reader – there appears to be no drivers currently.

Installing Puppy Linux to a USB Key on an Averatec 2370

  1. Download Puppy Linux from the Puppy Linux site. At the time of this writing, Puppy version 2.14 comes in a SeaMonkey edition and a Unleashed edition. The SeaMonkey is the standard Puppy with its default set of application. The Unleashed version allows you to custom configure your own Puppy live CD. Since Unleashed requires a spare partition and because I really don’t have time to fiddle with setting up a free partition, I am going to use the SeaMonkey edition.
  2. Burn Puppy to a CD. If you don’t have a burner software like Nero, you can download a freeware burner such as CD Burner Pro.
  3. Place the new CD into your computer and boot from the CD.
  4. When the CD boots, you’ll be prompted to enter the boot option. If you just wait, Puppy will boot into the default settings.
  5. Next you’ll be prompted to enter the keyboard layout. Select the one appropriate to your keyboard.
  6. Next you’ll be at the Puppy Video Wizard. You are given the choice for xorg or xvesa. If you select Xorg on the Averatec 2370, it will fail, so select Xvesa.
  7. The graphic should appear. Select the highest resolution at 1024x768x24 and press OK.
  8. Close the Puppy welcome window.
  9. Plug in the USB drive.
  10. Click on the drives icon, find the USB drive you inserted and press Mount.
  11. Select the menu item Menu->Setup->Puppy universal installer. This brings up the Puppy Universal Installer window.
  12. Select USB Flash drive and press OK.
  13. You’ll be prompted to select which drive to install to. Make sure you select the USB drive and press OK.
  14. Click on the normal install button.
  15. Press OK again when asked if you are sure.
  16. Press the CD button when ask where the Puppy files are located.
  17. Make sure the Puppy CD is in the drive, and press OK.
  18. When ask if you want to do with the MBR, select default and press OK.
  19. Select “Just Keep Going” and press OK.
  20. Press the enter key on the final sanity check.
  21. Press the enter key when finished.
  22. The CD will eject. Remove the CD, turn off machine and then turn it back on with the USB key in place. Press F11 when immediately after you switch on the machine. You’ll be prompted with a list of device to boot from.
  23. Select USB.

If everything works, you should end up being prompted to enter the keyboard. Repeat steps 5-7.

Getting the Network card to work with WPA-PSK

Averatec 2370 comes with a RT73 chipset, but Puppy does not automatically detect the right driver, so you have to explicitly install it. In addition, the network wizard does not work, at least not for WPA, so you have to edit the config filie /etc/Wireless/RT73STA/rt73sta.dat. You should also avoid clicking on scan network button. It does list all of the wireless access point in the area, but you can’t pick any of the access points on the listing and you can’t make the window go away.

  1. Click on the Setup icon.
  2. Click on “Connect to Internet by network interface…”.
  3. Click on Load Driver button.
  4. Make sure the Averatec wirelss switch is on. Select rt73 and press OK.
  5. You should get a message that loading has been successful. Press OK.
  6. In the Networ_Setup, you should see a rausb0 button. Normally, you would press the rausb0 and configure the wireless. For some reason, the GUI config does not work, so press the Exit button.
  7. Select Menu->File Managers->uXplor 2-Panel Manager.
  8. Browse to /etc/Wireless/RT73STA.
  9. Right click on the file “rt73sta.dat” and select the menu option “SendTo” and then select “Text Editor”.
  10. Edit the rt73sta.dat file and save. In my case, I have WPA-PSK using TKIP, so I needed to edit the fields SSID, AuthMode, EncrypType, and WPAPSK:
    SSID=<your access point’s ssid>
    AuthMode=WPAPSK
    EncrypType=TKIP
    WPAPSK=<the key>
  11. Click on the Setup icon.
  12. Click on “Connect to Internet by network interface…”.
  13. Click on the rausb0 button.
  14. Click on the Auto DHCP. There should be a brief pause and then you should get a dialog that the DHCP is successful. You are asked if you want to save the configuration.
  15. Press Yes.
  16. Press Exit to exit network setup.

Launch the browser and attempt to access the internet. The wirelss should now be working.

Installing Nvidia driver

Averatec 2370 comes with Nvidia 6100 video with a maximum resolution of 1280×800, but Puppy linux does not include the driver for the card. Puppy actually has two different Xserver: the standard Xorg and XVesa. XVesa is a light weight version of Xorg but does not support direct rendering and is limited to a resolution of 1024×768. Even without direct rendering, the machine appears fast enough to display movies on XVesa. If you can live witht he lower resolution, sticking with XVesa allow you to avoid tainting your kernal with the Nvidia proprietary driver.

A fellow Puppy user has made the Nividia driver into a dotpup file. Unfortunately, some tinkering is needed to get it to work. The following instructions are based on this post. Some manual editing of the xorg.conf file is needed to get the video working.

  1. Download the Nvidia dotpup file InstallNvidia.
  2. Select Menu->File Managers->Rox-Filter file manager.
  3. Browse to where you download the pup file and click on it to run the installer and press the Run button.
  4. You’ll be prompt to delete the pup file, I would press Yes to get rid of it or it will be save when you shutdown Puppy.
  5. Select Menu->Exit to Prompt.
  6. Type the command installnvidia to bring up the install screen.
  7. Options 1 does not work, so select option 3 to bring up the Puppy video wizard.
  8. Press xorg to bring up a list of monitors.
  9. Select “LCD Panel 1280×800” and press OK.
  10. Select the resolution 1280x800x24 and press OK. This takes us back to the installer screen.
  11. Select option 6 to install the 9629 driver.
  12. Select option 0 to exit to command line.
  13. Edit /etc/X11/xorg.conf.
  14. Scroll to the section “ServerLayout”, you’ll notice a line for “Screen 1” Right of “Screen0”. Delete this line.
  15. Scroll to the section “Monitor” with “Monitor1”. Delete this entire section.
  16. Scroll to the section “Device” with “Card1”. Delete this entire section.
  17. Save the file and exit the editor.
  18. Type modprobe agpgart. If you don’t, startx will fail, and you’ll get error messages about “unknown symbols”.
  19. Type startx to start up the GUI. You’ll notice the Nvidia logo briefly.

Enabling Averatec Power Management

ACPI seems to be enabled by default, but none of the ACPI modules are loaded. As a result, the fan is always on and the cpu runs at full speed, resulting in low battery life. To enable power management, due the following:

  1. edit the file /etc/rc.d/rc.modules.
  2. Locate the line [ ! -d /proc/acpi ] && modprobe apmChange the line to
    if [ -d /proc/acpi ];then
    modprobe ac
    modprobe battery
    modprobe button
    modprobe fan
    modprobe processor
    modprobe thermal
    modprobe powernow-k8
    modprobe cpufreq_conservative
    modprobe cpufreq_ondemand
    modprobe cpufreq_powersave
    modprobe cpufreq_userspace
    modprobe cpufreq_states
    else
    modprobe apm
    fi
  3. Save the changes.
  4. run the following command:echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor.

Configuring WMPower to run at Startup to track battery usage
Once the power management layer is in place, you you can run the wmpower application to display your battery level. To get wmpower to startup do the following:

  1. Edit the file /root/.xinitrc.
  2. Locate the line: exec $CURRENTWM
  3. Before this line, add the line:wmpower -no-meddling &The -no-meddling option tells wmpower to display status only. The ampersand is necessary to run the program in the background or the window manager won’t run.

Enabling the Touchpad
While the touchpad on Averatec 2370 is usable with the mouse driver. It is just way too sensitive. What we need to do is to load the Synaptic driver and edit the xorg.conf

  1. Open a command prompt.
  2. Type modprobe evdev
  3. In /etc/rc.d/rc.modules, add the following line to the end# Need to do this for Synaptics Touchpad

    modprobe evdev
  4. Edit /etc/X11/xorg.conf.
  5. In the section “Module”, add the following line to load the Synpatic driver.

    #Load Synaptic Module
    Load "synaptics"
  6. In the section “ServerLayout”, add the following line to make Syanptics the main pointer driver

    InputDevice "Touchpad" "CorePointer"
  7. Add the following section:
    Section "InputDevice"
    Driver "synaptics"
    Identifier "TouchPad"
    Option "Device" "/dev/input/psaux"
    Option "Protocol" "auto-dev"
    Option "MaxTapTime" "0"
    EndSection

    Note that I use MaxTapTime of 0 because I don’t like having a mouse click being generated by a touchpad tap. This often cause lots of problem during editing.
  8. Select Menu->Shutdown->Exit to Prompt to exit.
  9. Type startx to start the window manager. The touchpad should be working now.

Enabling the second USB Mouse
If you plug in a USB mouse into the Averatec 2370, the mouse is not automatically detected. If you examine what is returned by the dmesg command, you’ll notice that the USB device is detected, but there are no message that identifies the device as a mouse. To get it working, you’ll need to install the usbhid (usb human interface device) module and add the second mouse into xorg.conf.

  1. Open a command prompt.
  2. Type modprobe usbhid. If you dmesg, you’ll notice that the name and brand of your mouse is displayed.
  3. In /etc/rc.d/rc.modules, add the following line to the end# Need to do this for USB Mouse
    modprobe usbhid
  4. Edit /etc/X11/xorg.conf.
  5. In the section “ServerLayout”, add the following line to add the USB mouse driver
    InputDevice "USB Mouse" "AlwaysCore"
  6. Add the following section:
    Section "InputDevice"
    Driver "mouse"
    Identifier "USB Mouse"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "auto"
    Option "SendCoreEvents" "true"
    EndSection
  7. Select Menu->Shutdown->Exit to Prompt to exit.
  8. Type startx to start the window manager. The USB Mouse should be working now when you plug it in.

Installing Flash 9

Puppy 2.14 comes with Flash 7, but many of the site requires Flash 8 or later. To install the Flash 9, install the following dotpup.

January 29, 2007 at 2:14 am 6 comments

Older Posts


Calendar

August 2017
M T W T F S S
« Jun    
 123456
78910111213
14151617181920
21222324252627
28293031  

Posts by Month

Posts by Category