* Encrypted pup_saves are mounted as ext2 and not fscked. A comment in the init script says "#forum feedback this takes to long when encrypted..." That's a mis-understanding. When I posted that, some assumed I was talking about an encrypted pup_save, but it was non-encrypted with a lot of files.

Maybe you were talking non-encrypted, but I noticed a distinct slowdown when fsck'ing encrypted files.

My problem with that bit of code is that it stops doing fsck at all with encrypted files. I thought when we were talking about it, way back when, that we were going to fsck every 10th time or so for encrypted pupsaves.

On that download of the src code, I tried it too and it got truncated too. First time I ever ran into that. Wonder what is going on?

BTW I have to report a success. Got a Canon MP390 printer working using CUPS and the recipe at linuxprinting.org. First time printing with Puppy. Too bad the printer has a marginal print head.

Lobster, I haven't tested a parallel port printer, just assumed it works. Can you check that the 'lp' module is loaded, in a terminal window type 'lsmod'. It should be, if it isn't then we would have to chase down the reasons why not. If it isn't, try loading it, with 'modprobe lp' then run the CUPS Wizard.

Other than that, you printer needs to be turned on when you start the CUPS Wizard.

I booted the live cd in ram without access to a pup_save. Cups worked with a plain text doc from abiword on my parallel hp deskjet plus. Nice and quick. It didn't work from leafpad (as it did in 2.16) nor geany though. To add the printer in cups I selected dj 500 because my printer was not listed. Where is the hpij pet that the instructions mention?

Asus P5GC-MX board.
The network card won't run...Attansic L2.
Spent an hour on this including using your Windows driver wizard.
This included the setup files, program files, Windows installed files.
I can generally cheat Windows into getting drivers to work from
previous installations...where many others may fail.
So I know where to look for - inf - files.
This will be a future issue as people upgrade to this board as a new box is
so cheap...my customers machine cost $280 to upgrade...
DVD extra $50

- In This Release
- Building and Installation
- Command Line Parameters
- Additional Configurations
- Known Issues
- Support

In This Release
===============

This file describes the Linux* Base Driver for the Attansic(R) L2 Fast
Ethernet Adapter, version 1.0.x. This driver supports the 2.4.x and 2.6.x kernels.

This driver is only supported as a loadable module at this time. Attansic is not
supplying patches against the kernel source to allow for static linking of
the driver. For questions related to hardware requirements, refer to the
documentation supplied with your Attansic(R) adapter. All hardware
requirements listed apply to use with Linux.

Building and Installation
=========================

To build a binary RPM* package of this driver, run 'rpmbuild -tb
<filename.tar.gz>'. Replace <filename.tar.gz> with the specific filename of
the driver.

NOTE: For the build to work properly, the currently running kernel MUST match
the version and configuration of the installed kernel sources. If you
have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

1. Move the base driver tar file to the directory of your choice. For example,
use /home/username/atl2 or /usr/local/src/atl2.

2. Untar/unzip archive:

tar zxf atl2-x.x.x.tar.gz

3. Change to the driver src directory:

cd atl2-x.x.x/src/

4. Compile the driver module:

make install

The binary will be installed as:

/lib/modules/<KERNEL VERSION>/kernel/drivers/net/atl2.[k]o

The install locations listed above are the default locations. They might
not be correct for certain Linux distributions. For more information,
see the ldistrib.txt file included in the driver tar.

5. Install the module:

insmod atl2 <parameter>=<value>

6. Assign an IP address to the interface by entering the following, where
x is the interface number:

ifconfig ethx <IP_address>

7. Verify that the interface works. Enter the following, where <IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:

ping <IP_address>

Command Line Parameters
=======================

If the driver is built as a module, the following optional parameters are
used by entering them on the command line with the modprobe or insmod command
using this syntax:

modprobe atl2 [<option>=<VAL1>,<VAL2>,...]

insmod atl2 [<option>=<VAL1>,<VAL2>,...]

For example, with two L001 PCIE adapters, entering:

insmod atl2 TxMemSize=80,128
loads the atl2 driver with 8KB TX memory for the first adapter and 10KB TX memory
for the second adapter.

The default value for each parameter is generally the recommended setting,
unless otherwise noted.

NOTES: A descriptor describes a data buffer and attributes related to the
data buffer. This information is accessed by the hardware.

MediaType
Valid Range: 0-4
0 - auto-negotiate at all supported speeds
1 - only link at 100Mbps Full Duplex
2 - only link at 100Mbps Half Duplex
3 - only link at 10Mbps Full Duplex
4 - only link at 10Mbps Half Duplex
Default Value: 0
MediaType forces the line speed/duplex to the specified value in
megabits per second(Mbps). If this parameter is not specified or is set
to 0 and the link partner is set to auto-negotiate, the board will
auto-detect the correct speed.

RxMemBlock
Valid Range: 16-512
Default Value: 64
This value is the number of receice memory block allocated by the driver.
Increasing this value allows the driver to buffer more incoming packets.
Each memory block is 1536 bytes.

NOTE: Depending on the available system resources, the request for a
higher number of receive descriptors may be denied. In this case,
use a lower number.

TxMemSize
Valid Range: 4-64
Default Value: 8
This value is the number KB of transmit memory allocated by the driver.
Increasing this value allows the driver to queue more transmits.

NOTE: Depending on the available system resources, the request for a
higher number of transmit descriptors may be denied. In this case,
use a lower number.

FlashVendor
Valid Range: 0-2
Default Value: 0
This value standards on vendor of spi flash used by the adapter.
0 for Atmel, 1 for SST, 2 for ST

Additional Configurations
=========================

Configuring the Driver on Different Distributions
-------------------------------------------------

Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding
an alias line to /etc/modules.conf as well as editing other system startup
scripts and/or configuration files. Many popular Linux distributions ship
with tools to make these changes for you. To learn the proper way to
configure a network device for your system, refer to your distribution
documentation. If during this process you are asked for the driver or module
name, the name for the Linux Base Driver for the Attansic L2 is atl2

As an example, if you install the atl2 driver for two L2 adapters
(eth0 and eth1) and set the speed and duplex to 10full and 100half, add the
following to modules.conf:

alias eth0 atl2
alias eth1 atl2
options atl2 Speed=10,100 Duplex=2,1

Viewing Link Messages
---------------------

Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages
on your console, set dmesg to eight by entering the following:

dmesg -n 8

NOTE: This setting is not saved across reboots.

Known Issues
============

NOTE: For distribution-specific information, see the ldistrib.txt file
included in the driver tar.

Driver Compilation
------------------

When trying to compile the driver by running make install, the following
error may occur:

"Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source
tree and entering:

make include/linux/version.h.

Support
=======

For general information, go to the Attansic support website at:

http://support.attansic.com

If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to
the issue to xiong_huang@attansic.com

License
=======

This software program is released under the terms of a license agreement
between you ('Licensee') and Attansic. Do not use or load this software or any
associated materials (collectively, the 'Software') until you have carefully
read the full terms and conditions of the LICENSE located in this software
package. By loading or using the Software, you agree to the terms of this
Agreement. If you do not agree with the terms of this Agreement, do not
install or use the Software.

Want to report another success: I used the universal installer to put puppy on my PQI flash drive, and my pupsave, and booted properly off my USB 1.1 bus (a bit slow, but doable). This was something I gave up on a couple of revisions back because I never could get it to work. So that is very cool! Weird to boot a computer without the hard drive chattering away...

Only non-standard thing I did was that I used John Doe's latest wakepup2 found here:
http://www.murga-linux.com/puppy/viewtopic.php?p=122924#122924
because I needed the USB 1.1 support. I don't think 2.17B has that yet? Please put it in 2.17 if you can...

Two minor bobbles in the process. The dd to load the wakepup didn't work until I did a low-level format of the floppy. And I got the "It seems that the last time X ran..." message when I booted, which was strange because the last time I shut down I thought it came down properly. I guess that is /etc/.XLOADED.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum