Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 30 Sep 2014, 12:35
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Precise Puppy RC2, October 20, 2012
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 39 of 59 [875 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40, 41, ..., 57, 58, 59 Next
Author Message
Sage

Joined: 04 Oct 2005
Posts: 4790
Location: GB

PostPosted: Tue 11 Sep 2012, 14:48    Post subject:  

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.
Back to top
View user's profile Send private message 
shinobar


Joined: 28 May 2009
Posts: 2630
Location: Japan

PostPosted: Tue 11 Sep 2012, 16:38    Post subject: Re: bold or normal  

tiangeng wrote:
shinobar wrote:
tiangeng wrote:
how do I adjust for the bold style in precise?

http://www.murga-linux.com/puppy/viewtopic.php?p=650207#650207


Thanks!

Very good!

But I want to keep English font unchanged, and only need to adjust Chinese font, how should do?

What happened on your english fonts?

_________________
Google Chrome portable
Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
Back to top
View user's profile Send private message Visit poster's website 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Tue 11 Sep 2012, 18:41    Post subject: Driver for DGC USB analog modems  

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
dgcmodem-1.13-20120910.pet
Description  Woof part: kernel-independent components for driver release.
pet

 Download 
Filename  dgcmodem-1.13-20120910.pet 
Filesize  27.8 KB 
Downloaded  198 Time(s) 
rerwin_woof_fixes-delta-3d.pet
Description  Updated pupdial_init_hotpluggable script, to match DGC changes
pet

 Download 
Filename  rerwin_woof_fixes-delta-3d.pet 
Filesize  3.69 KB 
Downloaded  240 Time(s) 
dgcmodem-1.13-k3.2.28.pet
Description  Driver module only
pet

 Download 
Filename  dgcmodem-1.13-k3.2.28.pet 
Filesize  8.24 KB 
Downloaded  254 Time(s) 
dgcmodem-1.13-adapted-k3.tar.gz
Description  Source, updated for kernel 3.x, at least up to precise's kernel.
gz

 Download 
Filename  dgcmodem-1.13-adapted-k3.tar.gz 
Filesize  72.5 KB 
Downloaded  262 Time(s) 

Last edited by rerwin on Tue 11 Sep 2012, 20:31; edited 1 time in total
Back to top
View user's profile Send private message 
majorfoo

Joined: 07 Mar 2011
Posts: 445
Location: Wish I knew

PostPosted: Tue 11 Sep 2012, 20:02    Post subject:  

I have a problem trying to run xscreensaver in Precise Puppy

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   1065 Time(s)

xscreensaver-1.png

xscreensaver-2.png
 Description   
 Filesize   7.34 KB
 Viewed   1070 Time(s)

xscreensaver-2.png


Last edited by majorfoo on Tue 11 Sep 2012, 20:43; edited 2 times in total
Back to top
View user's profile Send private message 
majorfoo

Joined: 07 Mar 2011
Posts: 445
Location: Wish I knew

PostPosted: Tue 11 Sep 2012, 20:31    Post subject:  

Found my problem with above post.
Missing library = LibXxf86misc.so.1.1.0

Now works

Last edited by majorfoo on Fri 14 Sep 2012, 08:24; edited 1 time in total
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Tue 11 Sep 2012, 22:05    Post subject: Culmination of the Broadcom support project of 2012
Subject description: For module preferences and Peebee's "wl" multi-kernel driver package.
 

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:
    Code:
    NONPREFS="$(echo -n "$PREFLIST" | tr ' ' '\n' | grep -w -o ".*:${MODULE}$" | tail -n 1 | sed -e 's/:[^:]*$//' | tr : '\n')"


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.

Update 9/14/12: Re-uploaded 3f after downloads #4 and #1 (diff) to add fix-ID annotation to corrected statement. No functional change.
rerwin_woof_fixes-delta-3f.pet
Description  pup_event_backend_modprobe with extended preference processing.
Configuration files for Broadcom modules.
pet

 Download 
Filename  rerwin_woof_fixes-delta-3f.pet 
Filesize  7.93 KB 
Downloaded  242 Time(s) 
diff-pup_event_backend_modprobe-3f.txt.gz
Description  Difference file
gz

 Download 
Filename  diff-pup_event_backend_modprobe-3f.txt.gz 
Filesize  1.96 KB 
Downloaded  243 Time(s) 

Last edited by rerwin on Sat 15 Sep 2012, 18:19; edited 5 times in total
Back to top
View user's profile Send private message 
James C


Joined: 26 Mar 2009
Posts: 5794
Location: Kentucky

PostPosted: Wed 12 Sep 2012, 00:10    Post subject:  

Manual frugal install an an old P4 test box. All basics working and correct on initial boot.


# report-video
Report Video 1.3 - Tue 11 Sep 2012 on Precise Puppy 5.3.93 - Linux 3.2.28 i686

Chip description:
2.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
oem: Intel(r)865G Graphics Chip Accelerated VGA BIOS
product: Intel(r)865G Graphics Controller Hardware Version 0.0

X Server: Xorg Driver used: intel

X.Org version: 1.11.3
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 16 planes


...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
376 frames in 5.0 seconds = 75.020 FPS
376 frames in 5.0 seconds = 75.137 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 75.148 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 75.142 FPS

-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory : 512MB (149MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 11 Sep 2012 11:09:14 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH4 - Intel ICH5
Back to top
View user's profile Send private message 
Ray MK


Joined: 05 Feb 2008
Posts: 765
Location: UK

PostPosted: Wed 12 Sep 2012, 05:40    Post subject:  

Working very well on my 10yr old Acer laptop - thanks for a luvly Puppy.
_________________
Asus 701SD. 2gig ram. 8gb SSD. IBM A21m laptop. 192mb ram. PIII Coppermine proc. X60 T2400 1.8Ghz proc. 2gig ram. 80gb hdd. T41 Pentium M 1400Mhz. 512mb ram.
Back to top
View user's profile Send private message 
tiangeng

Joined: 23 Jul 2009
Posts: 61
Location: 河南 China

PostPosted: Wed 12 Sep 2012, 06:09    Post subject: Re: bold or normal  

shinobar wrote:
What happened on your english fonts?



Back to top
View user's profile Send private message 
LateAdopter

Joined: 27 May 2011
Posts: 155
Location: Reading UK

PostPosted: Wed 12 Sep 2012, 06:29    Post subject:  

Hello

There are a couple of kernel modules (cpuid & msr) that are not included in this puppy.

I would like to compile them, but I have never compiled anything before...

The source seems to be present in: /usr/src/linux-3.2.28/arch/x86/kernel

I had a look at m-a but I couldn't work out how to tell it what to build.

I'm sure it should only take a few lines of gibberish, typed into a terminal, to do it.

Would an expert tell me what they are, please?
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4790
Location: GB

PostPosted: Wed 12 Sep 2012, 06:33    Post subject:  

Any chance some kind soul could add Netgear FA311revD2 NIC to the list, please?
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 12 Sep 2012, 09:39    Post subject:  

Sage. That NIC uses natsemi.ko module.
/lib/modules/3.2.28/kernel/drivers/net/ethernet/natsemi/natsemi.ko

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.

Modinfo in my dpup, but the natsemi info is generic.
# modinfo natsemi
filename: /lib/modules/3.4.2-dpup/kernel/drivers/net/ethernet/natsemi/natsemi.ko
license: GPL
description: National Semiconductor DP8381x series PCI Ethernet driver
author: Donald Becker <becker@scyld.com>
alias: pci:v0000100Bd00000020sv*sd*bc*sc*i*
alias: pci:v0000100Bd00000020sv000012D9sd0000000Cbc*sc*i*
depends:
intree: Y
vermagic: 3.4.2-dpup SMP mod_unload modversions CORE2
parm: mtu:DP8381x MTU (all boards) (int)
parm: debug:DP8381x default debug level (int)
parm: rx_copybreak:DP8381x copy breakpoint for copy-only-tiny-frames (int)
parm: dspcfg_workaround:DP8381x: control DspCfg workaround (int)
parm: options:DP8381x: Bits 0-3: media type, bit 17: full duplex (array of int)
parm: full_duplex:DP8381x full duplex setting(s) (1) (array of int)
Back to top
View user's profile Send private message 
feelsub

Joined: 20 Jun 2012
Posts: 39

PostPosted: Wed 12 Sep 2012, 09:49    Post subject:  

Thanks Bary
beta 6 works nearly fine, but

audio bugs:
1/ http://murga-linux.com/puppy/viewtopic.php?p=651953
2/ http://murga-linux.com/puppy/viewtopic.php?t=80580
3/ enhancement suggestion
http://murga-linux.com/puppy/viewtopic.php?t=79829

Non US char errors in either copying or reading either on FAT or NTFS, no issues under WinXP or Win7
Quote:
File name is not a vaild UTF-8. You should rename it

In Rox these files/directories appear in red colour.
Names includes for instance : é è à ç or &
For instance, GNOME Player can't access those files.

Suggestion for laptop: a pop-up window when battery reach 9% and 3%, because I experienced the case to have a black-out (you don't necessarly notice the red battery indicator flashing).

I'll try again on next release.

Thanks
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Wed 12 Sep 2012, 10:09    Post subject:  

Quote:
Names includes for instance : é è à ç or &
For instance, GNOME Player can't access those files.

I have a testfile called ææøøøääööÅÅååÄÄ.JPG in ntfs partition.

It shows right in Precise Puppy 5.3.93 and also opens with Viewnior.

It looks like that it is accented character problem, not non US character problem.

For laptop usage with verbose warnings at certain battery state, vattery-acpitool with acpitool is the way to go...for instance. I had it in Upup Precise.
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4790
Location: GB

PostPosted: Wed 12 Sep 2012, 11:01    Post subject:
Subject description: Netgear FA311
 

pemasu : many thanks for that info. Dug it out of the depths of a rather old box!
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 39 of 59 [875 Posts]   Goto page: Previous 1, 2, 3, ..., 37, 38, 39, 40, 41, ..., 57, 58, 59 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 3.0352s ][ Queries: 13 (2.9223s) ][ GZIP on ]