I am using latest beta and this is slow compared to other Puppy's. I use a i5 2450M (I hope that is correct) and other Puppy's like Slacko (the latest) loads programs immediatelly while this Precise takes about two seconds per program to load. What is the problem with this Puppy? Regards.

I removed the saved file and now it all seems a lot faster. I had downloading a lot of useless stuff that might have started picking on Precise Puppy somehow. I guess the indexing service came from the KDE package I tried wishing that I could change X Desktop. Regards.

Barry,
While testing my upgraded versions of the Intel536/537 firmware packages, I found that the "stubbed" version of the modprobe_protect script does not allow for loading of modem modules that are not ready at the time their initialization scripts run. I have extended the --modcheck option to wait for pinstall scripts to complete and then wait for modules to appear in 'lsmod'. It also handles modules and their firmware force-loaded through the BootManager. It does not wait for modules loaded other than by backend_modprobe or the BootManager "addlist".

While testing that bugfix, I discovered that functions4puppy4 still looks for module name when searching the firmware.dep.inst list of firmware names. So, I corrected that.

With these bugfixes, the HSF and Intel modems should be detected on first boot after installation (when their upgraded firmware is included).
Richard

UPDATE 10/5/2012: Re-uploaded the modprobe_protect fix with corrected test for the presence of the waited-for module in the system. Please replace yesterday's version.

Barry,
Attached is a tarball containing 11 firmware pet-packages and one to clean out some residue. I have updated them all for consistency, in these ways:

- All /usr/sbin scripts and executables are moved from the all-firmware subdirectory to be installed to /usr/sbin at the time the package is installed.
- Packages for drivers loaded through udev rules (1) remove copied firmware files if the driver is not present and (2) contain their respective portion of the "dialup modem" rule that triggers loading.
- Where config files were written in the pinstall script (pctel, mwave), they are now already present in the firmware directory, to allow normal uninstallation.
- All configuration files are prefixed by "modemx" to retain them across a pupdial "erase" but remove them if a second erase is performed (i.e., pupdial already shows no modem detected).

I have tested the packages for modems I have and for which there are drivers for precise: DGC, ESS, HSF, intel536, intel537, intel8x0m (uses slmodemd daemon). Most of these benefit from the "protect" bugfix posted above, but do not require it; without it, the modem may not be detected on the first boot-up after package installation or after an "erase".

Because the packages in the tarball are at the top level, testers/users should probably expand the tarball into a dedicated directory, to keep the packages together.
Richard

Testers & users,
Attached are driver modules that compile and "work" in precise pup. The linuxant drivers are already provided on page 44 of this thread. Although the ESS driver "just works", the intel53x drivers are another story.

The Intels consist of 6 versions, each of which must be specific to the CPU configuration (12, total)! They must be used in uniprocessor or multi-core/processor PCs as versions that match -- "uni" or SMP. They must have been compiled with appropriate (uni/SMP) kernel source. The developer warns that ignoring that constraint can cause the PC to "crash". Because precise beta7 uses an SMP kernel, the intel536/intel537 drivers are compiled for use only by multiprocessor/multicore systems. My uniprocessor PC with the 536 locked up when I disconnected after a very successful connection to my ISP. That did not happen with the 537 because it does not detect a dial tone (due to a known problem with it).

But not to worry! The upgraded firmware packages for them enforce the rules so that the correct version is used if present, or else the modem is shown as not being detected. The attached intel drivers should work reliably on a multi-core/processor system, although I am unable to verify that (having no multicore tower PCs).

Note that the intel537 I attach is only for the "537EP" variant. The others are 537, 537SP, 537EA and 537AA. If anyone needs the driver for one of those others, please send me a PM and I will add it to this posting.
Richard

Barry,
Here are the source tarballs used to compile the above drivers.

After module creation, the Intel536 and Intel537 .ko files should be renamed to replace "ko" with "HIDE", for compilations made for an SMS-type kernel, and "HIDEUNI" for those compiled for a uniprocessor-type kernel. I notice that there is a new (to us) variant of the intel537, the 537AA. (The upgraded firmware package accounts for it.)

I would like to create a "build modem drivers" script to automate the special handling of the linuxant, intel and agere-HDA drivers, but do not want to duplicate any system you might already have to do that. I do not know the workings of woof and your driver-build process, so would like to add my information to whatever you might have to start with.
Richard

Update 10/14/2012: The ESS source tarball replaces the version previously posted on page 48. The original was compressed after the driver was built, so unnecessarily contained the results of that build. A "make clean" was run to remove those artifacts (reducing size from 900+ KB to 200+ KB).Last edited by rerwin on Sun 14 Oct 2012, 11:51; edited 1 time in total

Barry,
Thank you for accepting all of my submitted packages and for correcting and fleshing out the pinstalls and pet_specs. Using your intel537ep driver package as a model, I am attaching driver packages for the remaining 4 flavors of the 537.
Richard

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