Wary Puppy 5.1.4 - 29 August 2011

[BarryK]

When I upgraded my frugal installation of 5.1.2 to 5.1.3, everything seemed to work well, but I soon found that my wireless did not work. When I tried to redefine my connection, my wireless adapter (ath5k) did not show up. Trying to manually load the kernel module gave me an error (see attached).

When I removed the warysave file and rebooted into a clean 5.1.3, everything worked perfectly - my wireless card is detected and works.

No problems to report otherwise - looks like another solid release!

Ah, yes, this is a problem that I thought might happen. There are modules left behind in /lib/modules/2/6/32, from the old kernel.

When I compiled 2.6.32-44 for latest Wary, there were configure changes. Modules from the old kernel might not load.

You can fix it manually in your save-file by going into /initrd/pup_rw/lib/modules/2.6.32 and delete everything then reboot.

[BarryK]

So? 8139cp:8139too means that the second one has preference, that is, 8139too has preference.

Yes, indeed. That is what it was originally. It didn't work. tp suggested swapping the order. That didn't work. As a mere user, I followed implicitly the suggestions of the guy who tried to help in the expectation that it might help other folks who had experienced problems. At that stage, PREFLIST in file /etc/rc.d/MODULESCONFIG wasn't mentioned. I don't do coding - I have to explain this frequently. I was blissfully unaware that something else needed changing.
I report things that don't work - as requested. A bunch of guys who do the coding look into making their great distros even greater. That way, we all get better reviews and a larger user base. Meanwhile, I am happy to assist anyone struggling with conformational analysis, rate equations, etc, etc.................

The preferences setting in BootManager is only a GUI frontend for PREFLIST in file /etc/rc.d/MODULESCONFIG. So, you make a change to the preferences list in BootManager, it ends up in /etc/rc.d/MODULESCONFIG.
Those who know that can opt to edit /etc/rc.d/MODULESCONFIG directly.

[BarryK]

frugal-install Wary513 on USB-Flash via syslinux (without hard disk)
Result: I can't boot. message error: puppy_wary_5.1.3.sfs not found. Dropping out initram...

This is my syslinux.cfg

Code: Select all

label 00
kernel /wary513/vmlinuz pdev1=sdb1 psubdir=wary513
append initrd=/wary513/initrd.gz 

label 01
kernel /wary513/vmlinuz pdev1=sdb1 pmedia=sdb1 psubdir=wary513
append initrd=/wary513/initrd.gz 

Same errors if I install Wary513 via grub4Dos!

Any suggestions to path this bug (syslinux, grub4Dos or initrd.gz ...?)
Thank you

*** Oh, I'd discovered this error comes with other distros: slacko, popularpup, midnightpup ... Must be leave with USB-Flash install?

You are booting from USB, the drive letters can change depending on what USB drives are plugged in. So, take out the "pdev=sdb1", it isn't needed anyway.

pmedia=sdb1 is wrong. Take that out also. Or, change it to "pmedia=usbflash" or "pmedia=usbhd".

The allowed values for pmedia are
usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cd

[BarryK]

Hi all,
Has anybody had success with the delta files.
I downloaded the 5.1.2__5.1.3delta file from ibiblio from Barry's blog link and tried to build an iso using Xdiff Manager. Something I have successfully done numerous times before. A window came up saying the iso had been built, but it was telling porky pies, there was no new iso. this was in Wary_5.1.2.7, so I shut down and tried again in Lupu 5.2.5, same result.
Looked about for any error reporting and found a report at /temp/xdelta-err which said "xdelta3: target window cheksum mismatch: XD3_INVALID_INPUT".
Did an md5sum on the delta file, output agreed with that posted on ibiblio.
Now confused.
Cheers

I have checked this, running Wary 5.1.2 and 5.1.2.7, works both times.

These are the md5sums:

# md5sum wary-5.1.2.iso
f0443db6b1f7dce2e4160198c812d7e5 wary-5.1.2.iso
# md5sum wary-5.1.2.iso___wary-5.1.3.iso.delta
9fc09446c6fc373df929c60ec9985fff wary-5.1.2.iso___wary-5.1.3.iso.delta
# md5sum wary-5.1.3.iso
ba887afece44e6e3c19e0ce9eeeb360c wary-5.1.3.iso

...md5sum of the generated wary-5.1.3.iso is correct.

[01micko]

Hi Barry

This is my extlinux.conf, straight out of Puppy Universal Installer (PUI)

Code: Select all

default puppy
display boot.msg
prompt 1
timeout 50

F1 boot.msg
F2 help.msg
F3 help2.msg

label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=usbflash

No hard drive and I get dropped to initial ramdisk console.

I also note a bug where if you use PUI to install to FAT32 usb pen drive then it is not bootable (I tried a few of the mbr options) however, if I overwrite that install with one using BootFlash the drive is bootable (BUT not with no hard drive). Linux filesystems work fine (again not without a hard drive).

These bugs are apparent in latest Wary 513 and spup-312.37 (woof from August 8 I think).

Cheers

[Sage]

The preferences setting in BootManager is only a GUI frontend for PREFLIST

Many thanks for that clarification.
That leaves a major question mark, doesn't it. Why did I run into show-stopping 8139 C&D NIC problems with Waries < 5.1.3, in common with other folks, but the latter version signed them all on immediately? Furthermore, the prior Wary problems responded neither to considered guru nor mindless idiot fiddling?

[pemasu]

When I tested bootflash script in console in my dpup, I noticed that the script tried to use mbrfat.bin which wasnt included in syslinux package I used.
So I made symlink to mbr.bin which has been working for me.

[vanchutr]

Thank you sir Barry Kauler.
I'd follwed your instructions (about booting with usb-flash). But no success!
I want to emphasize: "There is'nt hard disk on my computer".
But I can boot your puppy_sqzd_4.4.99.2 with syslinux (without hard disk). This is my syslinux.cfg file

Code: Select all

label 06
kernel /barry/vmlinuz 
append initrd=/barry/initrd.gz psubdir=barry

[01micko]

vanchutr

Barry knows why now..

http://bkhome.org/blog/?viewDetailed=02409

[vanchutr]

Thank you 01micko, Barry
I'll learn from you

[BarryK]

Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.

Nathan's wallpaper setter as used in other puppies does not have his problem.

cheers
peebee

The next Wary will have Nathan's Wallpaper Setter.

You can install it in the PPM, puppy-common repo. Version 0.6.1 is latest.

[BarryK]

Barry,
During lupu testing, I discovered and fixed two issues that can also benefit wary and woof.

1. Pupscan produces confusing "kernel module" information from the lspci command. In actuality, lspci lists both "kernel modules" and "kernel drivers", the latter, I assume, being drivers built into the kernel. I adapted pupscan's formatting to handle this. Currently, my PCI adapters are described as:

• DESCRIPTION: Host bridge: Silicon Integrated Systems [SiS] 746 Host
  VENDOR: 1039 DEVICE: 0746
  KERNEL MODULE: agpgart-sis
  
  KERNEL MODULE: sis-agp
  
  DESCRIPTION: PCI bridge: Silicon Integrated Systems [SiS] SG86C202
  VENDOR: 1039 DEVICE: 0002
  KERNEL MODULE: shpchp
  
  DESCRIPTION: ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO]
  VENDOR: 1039 DEVICE: 0963
  DESCRIPTION: SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
  VENDOR: 1039 DEVICE: 0016
  KERNEL MODULE: i2c-sis96x
  
  DESCRIPTION: IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
  VENDOR: 1039 DEVICE: 5513
  KERNEL MODULE: pata_sis
  
  DESCRIPTION: Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller
  VENDOR: 1039 DEVICE: 7012
  KERNEL MODULE: Intel ICH
  
  KERNEL MODULE: snd-intel8x0
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL MODULE: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL MODULE: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
  VENDOR: 1039 DEVICE: 7002
  KERNEL MODULE: ehci_hcd
  
  DESCRIPTION: Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
  VENDOR: 1039 DEVICE: 0900
  KERNEL MODULE: sis900
  
  KERNEL MODULE: sis900
  
  DESCRIPTION: Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
  VENDOR: 8086 DEVICE: 1080
  DESCRIPTION: VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 460]
  VENDOR: 10de DEVICE: 0170

With the fix they are:

• DESCRIPTION: Host bridge: Silicon Integrated Systems [SiS] 746 Host
  VENDOR: 1039 DEVICE: 0746
  KERNEL DRIVER: agpgart-sis
  KERNEL MODULE: sis-agp
  
  DESCRIPTION: PCI bridge: Silicon Integrated Systems [SiS] SG86C202
  VENDOR: 1039 DEVICE: 0002
  KERNEL MODULE: shpchp
  
  DESCRIPTION: ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO]
  VENDOR: 1039 DEVICE: 0963
  
  DESCRIPTION: SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
  VENDOR: 1039 DEVICE: 0016
  KERNEL MODULE: i2c-sis96x
  
  DESCRIPTION: IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
  VENDOR: 1039 DEVICE: 5513
  KERNEL DRIVER: pata_sis
  
  DESCRIPTION: Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller
  VENDOR: 1039 DEVICE: 7012
  KERNEL DRIVER: Intel ICH
  KERNEL MODULE: snd-intel8x0
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL DRIVER: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL DRIVER: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
  VENDOR: 1039 DEVICE: 7002
  KERNEL DRIVER: ehci_hcd
  
  DESCRIPTION: Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
  VENDOR: 1039 DEVICE: 0900
  KERNEL DRIVER: sis900
  KERNEL MODULE: sis900
  
  DESCRIPTION: Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
  VENDOR: 8086 DEVICE: 1080
  
  DESCRIPTION: VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 460]
  VENDOR: 10de DEVICE: 0170

Although the updated script is in the attachment, to assist with merging the changes into your updated version of pupscan, here is the difference listing:

Code: Select all

--- pup_ro2/usr/sbin/pupscan	2010-12-26 16:05:14.000000000 -0500
+++ pup_rw/usr/sbin/pupscan	2011-08-14 14:39:01.000000000 -0400
@@ -7,6 +7,7 @@
 #v431 rerwin: Add --silent option to only generate files, without display.
 #100108 BK 'scanpci' is not working properly xorg 7.5. actually it is no longer part of libpciaccess pkg.
 #101221 yaf-splash fix.
+#110814 rerwin: distinguish kernel driver from module for lspci formatting.
 
 [ "`echo $@ | grep ' *--silent *'`" != "" ] && SILENT=true || SILENT=false #v431
 KERNVER="`uname -r`"
@@ -120,18 +121,23 @@
   done
  fi
 else
+ FIRSTSET=true #110814
  lspci -nn -k | tr '|' ' ' | tr -s ' ' | tr '\t' '|' | grep -v 'Subsystem: ' |
  while read ONELINE
  do
   if [ "`echo "$ONELINE" | cut -c 1`" != "|" ];then
+   [ $FIRSTSET = true ] || echo >> /tmp/chipnummod.txt #110814
    DESCRIPTION="DESCRIPTION: `echo -n "${ONELINE}" | cut -f 2-99 -d ' ' | rev | cut -f 2-9 -d '[' | rev | sed -e 's% \[.*\]:%:%'`"
    echo "$DESCRIPTION"  >> /tmp/chipnummod.txt
    CHIPNUMS="VENDOR: `echo -n "$ONELINE" | rev | cut -f 1 -d '[' | cut -f 2 -d ']' | rev | sed -e 's%:%  DEVICE: %'`"
    echo "$CHIPNUMS"  >> /tmp/chipnummod.txt
+   FIRSTSET=false #110814
   else
-   KMODULE="KERNEL MODULE:`echo "$ONELINE" | rev | cut -f 1 -d ':' | rev`"
-   echo "$KMODULE"  >> /tmp/chipnummod.txt
-   echo  >> /tmp/chipnummod.txt
+   echo "$ONELINE" | grep -q 'driver' \
+    && KLABEL="KERNEL DRIVER" \
+    || KLABEL="KERNEL MODULE" #110814
+   KNAME="`echo "$ONELINE" | rev | cut -f 1 -d ':' | rev`" #110814
+   echo "$KLABEL: $KNAME"  >> /tmp/chipnummod.txt #110814
   fi
  done
 fi

Richard,
I applied your patch to pupscan, however my lspci does not distinguish between builtin drivers and modules. For example, with your patched pupscan:

Code: Select all

DESCRIPTION: Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) 
VENDOR: 168c  DEVICE: 002e
KERNEL DRIVER:  ath9k

But ath9k is a module.

[BarryK]

Richard,
Here is my lspci output:

Code: Select all

# lspci -nn -k | tr '|' ' ' | tr -s ' ' | tr '\t' '|' | grep -v 'Subsystem: '
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02)
|Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express x16 Root Port [8086:0045] (rev 02)
|Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
|Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05)
|Kernel driver in use: HDA Intel
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
|Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 05)
|Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
|Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b09] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller [8086:3b29] (rev 05)
|Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 05)
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 05)
01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0df1] (rev a1)
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe [14e4:1692] (rev 01)
03:00.0 Network controller [0280]: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01)
|Kernel driver in use: ath9k
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02)
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02)
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02)
ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 02)
ff:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 02)
ff:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 02)
# 

[rjbrewer]

Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.

Nathan's wallpaper setter as used in other puppies does not have his problem.

cheers
peebee

The next Wary will have Nathan's Wallpaper Setter.

You can install it in the PPM, puppy-common repo. Version 0.6.1 is latest.

I added new backgrounds with Pwallpaper; no problem.

[BarryK]

Barry,
During lupu testing, I discovered and fixed two issues that can also benefit wary and woof.

1. Pupscan produces confusing "kernel module" information from the lspci command. In actuality, lspci lists both "kernel modules" and "kernel drivers", the latter, I assume, being drivers built into the kernel. I adapted pupscan's formatting to handle this. Currently, my PCI adapters are described as:

• DESCRIPTION: Host bridge: Silicon Integrated Systems [SiS] 746 Host
  VENDOR: 1039 DEVICE: 0746
  KERNEL MODULE: agpgart-sis
  
  KERNEL MODULE: sis-agp
  
  DESCRIPTION: PCI bridge: Silicon Integrated Systems [SiS] SG86C202
  VENDOR: 1039 DEVICE: 0002
  KERNEL MODULE: shpchp
  
  DESCRIPTION: ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO]
  VENDOR: 1039 DEVICE: 0963
  DESCRIPTION: SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
  VENDOR: 1039 DEVICE: 0016
  KERNEL MODULE: i2c-sis96x
  
  DESCRIPTION: IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
  VENDOR: 1039 DEVICE: 5513
  KERNEL MODULE: pata_sis
  
  DESCRIPTION: Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller
  VENDOR: 1039 DEVICE: 7012
  KERNEL MODULE: Intel ICH
  
  KERNEL MODULE: snd-intel8x0
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL MODULE: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL MODULE: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
  VENDOR: 1039 DEVICE: 7002
  KERNEL MODULE: ehci_hcd
  
  DESCRIPTION: Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
  VENDOR: 1039 DEVICE: 0900
  KERNEL MODULE: sis900
  
  KERNEL MODULE: sis900
  
  DESCRIPTION: Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
  VENDOR: 8086 DEVICE: 1080
  DESCRIPTION: VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 460]
  VENDOR: 10de DEVICE: 0170

With the fix they are:

• DESCRIPTION: Host bridge: Silicon Integrated Systems [SiS] 746 Host
  VENDOR: 1039 DEVICE: 0746
  KERNEL DRIVER: agpgart-sis
  KERNEL MODULE: sis-agp
  
  DESCRIPTION: PCI bridge: Silicon Integrated Systems [SiS] SG86C202
  VENDOR: 1039 DEVICE: 0002
  KERNEL MODULE: shpchp
  
  DESCRIPTION: ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO]
  VENDOR: 1039 DEVICE: 0963
  
  DESCRIPTION: SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
  VENDOR: 1039 DEVICE: 0016
  KERNEL MODULE: i2c-sis96x
  
  DESCRIPTION: IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
  VENDOR: 1039 DEVICE: 5513
  KERNEL DRIVER: pata_sis
  
  DESCRIPTION: Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller
  VENDOR: 1039 DEVICE: 7012
  KERNEL DRIVER: Intel ICH
  KERNEL MODULE: snd-intel8x0
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL DRIVER: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
  VENDOR: 1039 DEVICE: 7001
  KERNEL DRIVER: ohci_hcd
  
  DESCRIPTION: USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
  VENDOR: 1039 DEVICE: 7002
  KERNEL DRIVER: ehci_hcd
  
  DESCRIPTION: Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
  VENDOR: 1039 DEVICE: 0900
  KERNEL DRIVER: sis900
  KERNEL MODULE: sis900
  
  DESCRIPTION: Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
  VENDOR: 8086 DEVICE: 1080
  
  DESCRIPTION: VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 460]
  VENDOR: 10de DEVICE: 0170

Although the updated script is in the attachment, to assist with merging the changes into your updated version of pupscan, here is the difference listing:

Code: Select all

--- pup_ro2/usr/sbin/pupscan	2010-12-26 16:05:14.000000000 -0500
+++ pup_rw/usr/sbin/pupscan	2011-08-14 14:39:01.000000000 -0400
@@ -7,6 +7,7 @@
 #v431 rerwin: Add --silent option to only generate files, without display.
 #100108 BK 'scanpci' is not working properly xorg 7.5. actually it is no longer part of libpciaccess pkg.
 #101221 yaf-splash fix.
+#110814 rerwin: distinguish kernel driver from module for lspci formatting.
 
 [ "`echo $@ | grep ' *--silent *'`" != "" ] && SILENT=true || SILENT=false #v431
 KERNVER="`uname -r`"
@@ -120,18 +121,23 @@
   done
  fi
 else
+ FIRSTSET=true #110814
  lspci -nn -k | tr '|' ' ' | tr -s ' ' | tr '\t' '|' | grep -v 'Subsystem: ' |
  while read ONELINE
  do
   if [ "`echo "$ONELINE" | cut -c 1`" != "|" ];then
+   [ $FIRSTSET = true ] || echo >> /tmp/chipnummod.txt #110814
    DESCRIPTION="DESCRIPTION: `echo -n "${ONELINE}" | cut -f 2-99 -d ' ' | rev | cut -f 2-9 -d '[' | rev | sed -e 's% \[.*\]:%:%'`"
    echo "$DESCRIPTION"  >> /tmp/chipnummod.txt
    CHIPNUMS="VENDOR: `echo -n "$ONELINE" | rev | cut -f 1 -d '[' | cut -f 2 -d ']' | rev | sed -e 's%:%  DEVICE: %'`"
    echo "$CHIPNUMS"  >> /tmp/chipnummod.txt
+   FIRSTSET=false #110814
   else
-   KMODULE="KERNEL MODULE:`echo "$ONELINE" | rev | cut -f 1 -d ':' | rev`"
-   echo "$KMODULE"  >> /tmp/chipnummod.txt
-   echo  >> /tmp/chipnummod.txt
+   echo "$ONELINE" | grep -q 'driver' \
+    && KLABEL="KERNEL DRIVER" \
+    || KLABEL="KERNEL MODULE" #110814
+   KNAME="`echo "$ONELINE" | rev | cut -f 1 -d ':' | rev`" #110814
+   echo "$KLABEL: $KNAME"  >> /tmp/chipnummod.txt #110814
   fi
  done
 fi

Richard,
I applied your patch to pupscan, however my lspci does not distinguish between builtin drivers and modules. For example, with your patched pupscan:

Code: Select all

DESCRIPTION: Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) 
VENDOR: 168c  DEVICE: 002e
KERNEL DRIVER:  ath9k

But ath9k is a module.

Ok, I have done it, pupscan now distinguishes between builtin drivers and modules. Will be uploaded with next Woof.

[Sage]

Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.

Both rjbrewer and I have no problems with Pwallpaper - both recorded above. Lack of response from peebee might be due to a local issue? Nathan/Pwall - as long as it works...

[peebee]

Both rjbrewer and I have no problems with Pwallpaper - both recorded above. Lack of response from peebee might be due to a local issue? Nathan/Pwall - as long as it works...

Here for the interest of sage and rjbrewer is a screen shot showing my Pwallpaper problem.

As you can see I have copied a background called ORIGINAL-Third.jpg into /usr/share/backgrounds and then opened Pwallpaper where this file is nowhere to be seen............

Cheers
peebee

[smokey01]

Try renaming it. Maybe it doesn't like all of those capital letters.

Who knows, maybe it will provide a clue.

[Sage]

You cite your file as an .jpg, but your screen asks for a .png ? Have you tried converting your jpeg to the FSF picture format? Plenty of utilities around to inter-convert formats.
There can be other aspects to screw up displaying wallpapers, like size/res/ etc. I am no graphics expert but there'll be one along anytime soon.

[Billtoo]

I used the latest woof (aug 15th) to build wary 513 and the only
change I made was to use the 2.6.39.3 pae kernel.
It is working great,feels unbreakable.
Tue 16 Aug 2011 Operating System: Wary Puppy-5.1.3 Linux 2.6.39