Couple of other features have appeared in the last two betae:
PS/2 mouse remains stationary after first liveCD load; generally works at second ask (no saved data, though). USB wi-fi undetected until second USB item plugged in.
Weird and very new.

Barry, et al,
Now that I think I have completed the HSF modem package testing and fixing, I now attach similar packages for the DGC (CDC ACM) USB modems. The dgcmodem driver is actually only a "wrapper" around the cdc_acm module, in that it apparently handles "off-spec" models that use the Conexant DGC chipset. It seems to pass through "in-spec" models, so can apparently handle all cdc-acm devices.

My test modem works with- or without the DGC driver, so must be a normal model. So, I cannot verify that it actually makes the non-standard models work. I see in ubuntu threads that the Zoom 3095 has needed the DGC driver. If that is still true, and any of you have such a modem, could you test precise without- and with these upgraded dgcmodem packages?

In this upgrade for kernel 3.x, I have made minor corrections, one of which you might notice. Previously, a ttyACMx modem might not be detected during first boot-up, resulting in the need to tick a box during setup to force detection of the ttyACMx modem. Now the ttyACMx should always appear as detected on the first boot of a new puppy environment. The old behavior was a mistake on my part due to confusion over the addition of the hotplug script.

Another correction relates to the HSO modems, but makes only a subtle difference, if any. During hotplugging, the HSO modem should now be detected before any other that might also be plugged in. This matches the boot-time detection priority. (Since I cannot test this, I updated only the order of probing in 2 variable strings, and moved the HSO code section to first in the section group, eliminating the need for a "flag".)

The third correction maintains DGC-modem functioning as it was, compensating for a change in data available to the DGC initialization script and corresponding pupdial...hotplug... section. A message needed for detection of a DGC modem is no longer present in the message log, making the Dgcmodem init script ineffective. In fact, I suspect that it has not been effective for a long time, because the Cdcacm script executed before it and always found the modem. Therefore, I removed the Dgcmodem script altogether, along with its pupdial...hotplug... counterpart. The dgcmodem pinstall script now simply copies the Cdcacm script into /etc/init.d from the cdcacm firmware/tarball directory, avoiding maintenance of a duplicate script.

I hope that these packages as well as the HSF set can be considered for woof. Tester feedback might build confidence in these upgraded packages.
Richard

When I first try to start xscreensaver, I receive the xscreensaver-1.png error

If I select ok on the xscreensaver-1.png, I then receive xscreensaver-2.png error

I have installed xscreensaver in many versions of the luci/lucid series, Dpup series, Slacko series, etc and program has been working great on all of these until recently. Possible this has something to do with the latest kernel, since it will not work on Slacko-5.3.5.3 and now the latest Precise series.

Anyway, I would appreciate any help that would point me in the right direction.

xscreensaver-1.png

Description

Filesize

8.27 KB

Viewed

1371 Time(s)

xscreensaver-2.png

Description

Filesize

7.34 KB

Viewed

1275 Time(s)

Last edited by majorfoo on Tue 11 Sep 2012, 20:43; edited 2 times in total

Barry, Broadcom wifi users,
After about 8 months of experimentation, I (with much help from peebee, stu91 and others) have arrived with a "puppy infrastructre" solution to the various issues around Broadcom 43xx wifi cards. It originated with Piratesmack's concept of unloading then reloading conflicting drivers to ensure that competing modules are always loaded in a particular sequence, to avoid interference among them. For the setup to be ready for automated network setup, the activity must be accomplished very early during module loading. The idea was tested thoroughly using complex modprobe configuration files to perform the reloads at the time a priority module is modprobed. The attached solution moves most of the config-file logic into the module loader, pup_event_backend_modprobe.

The logic's inclusion in backend_modprobe makes it available for all conflicting modules represented by preference specifications in MODULESCONFIG, to allow any combination of a preference set to be active but always loaded in priority order. This is appropriate for cases where modules' device coverage overlaps but not completely, to allow both (preferred and nonpreferred) devices to operate. In testing, I found a case where it also ensures module order during initial use of a device that requires extensive firmware/pinstall setup -- the dgcmodem driver is intended to load before cdc_acm but is preceded by cdc_acm while the pinstall processing occurs, which the "reload" logic now corrects.

The reload logic should be a "last resort" for ensuring module load order. To minimize the need for it, a 1-second delay is added to the loading of a "nonpreferred" module to allow time for a possible preferred counterpart to load. To allow both to load, the preference-determination code is changed to avoid session-permanent blacklisting of nonpreferreds. All of this should reduce instances of rare-but-unexpected interference among modules during startup.

The Broadcom wifi devices use modules (ssb, bcma) that get loaded very early, before the normal event-driven loading takes place, leaving no option other than reloading them when necessary (when wl loads).

To track special actions taken for modules related to "preferences", the activities are logged with millisecond time tags to /tmp/pup_event_backend/preferences.log. (That's how I discovered the dgcmodem-cdc_acm reversal.)

The backend_modprobe changes are accompanied by small modprobe-configuration files for b43, b43legacy, brcmsmac and wl, to handle their special needs. The included pmodemdiag diagnostic script adds the preferences log to the diag file.

This package should be tried for any case where a module-preference is in effect. usually for wifi devices suported by multiple drivers. Broadcom brcm43xx users can install peebee's wl driver and verify that it works as well as it did with the "experiments". Instructions for obtaining and installing peebee's "bare-bones" multi-kernel driver packages are here:
http://murga-linux.com/puppy/viewtopic.php?t=76495&start=36

I hope that after some testing and validation by interested parties this package can be considered for addition to woof. Thank you to all who have assisted in getting this implementation to this point, and to those who now use it.
Richard

How does this work with the preference list? ADDED:

- To determine driver priority for a particular device, the preference list (PREFLIST in MODULESCONFIG) is scanned to find an entry for the "detected" module. The scan has depended on a single entry for each module with alternatives -- multiple entries could cuse an unexpected result. This upgrade enforces that assumption, so that any subsequent entry for the same detected module is ignored.

- Determination of the "reload" priority uses the list "in reverse". It is effectively scanned right-to-left for all instances of a module as the most preferrred. The modules included in each such preference entry are candidates for being reloaded if already loaded. Although this may require entries specifically for the "reload" operation, the current preferences will trigger a reload if necessary.

- For the Broadcom case, the preferences are "ssb:wl bcma:wl ssb:bcma", because wl is preferred over both ssb and bcma. While the "ssb:bcma" has not been necessary because no conflict exists between them, it indicates that if both are loaded, bcma must load first. The "reverse scan" for wl will find bcma, then ssb, to be loaded in that order; the scan for bcma will find ssb.

- Considering that the user could inadvertently change the order of the preference entries and change the reload sequence, that risk could be reduced by limiting the reverse-scan to only the last entry specifed, forcing the full sequence to be contained in the last preference for (say) wl. The preference entries would then be: "bcma:wl ssb:bcma:wl", again with the "ssb:bcma" part never being effective in preference determination, only for reloads. To make this change, line 244 should include "| tail -n 1 " to become:

UPDATE 9/13/2012: Replaced the fix package with corrected version 3f. Those of you who downloaded fix-3e, please replace it with this version. Otherwise, module-preference processing will not work. I inadvertantly omitted a critical argument during merging of the mods into the latest version of the backend_modprobe script.

So....the driver has been included but it seems to have reputation of only partial support to the devices it should support. I am afraid there isnt solution. Or....someone should create better driver...and since that card seems to be at least 10 years old...the support might be not so expected.
The scyld seems to be the organization behind that support.

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