Precise Puppy RC2, October 20, 2012

[Billtoo]

I did a manual frugal install to the hard drive.

Report Video 1.3 - Mon 10 Sep 2012 on Precise Puppy 5.3.93 - Linux 3.2.28 i686

Chip description:
2.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
oem: Intel(R)Ironlake Desktop Graphics Chipset Accelerated VGA BIOS
product: Intel(R)Ironlake Desktop Graphics Controller Hardware Version 0.0

X Server: Xorg Driver used: intel

X.Org version: 1.11.3
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 16 planes

I gave ppm a try and downloaded VLC, it didn't take long and is
working great.
Just beginning to test but looking good so far.

[tiangeng]

I have one more suggestion. In Racy, upgrade Ghostscript from here..

Then try the Gutenprint driver again.

Address Not Found

www.datafilehost.com could not be found.

Probably blocked in China.

Try here.

very good!
Yozo_office print with no problem!

[rcrsn51]

very good! Yozo_office print with no problem!

Excellent! Is that with the Gutenprint driver? Will it also print with the HP Postscript driver from page 32?

[tiangeng]

very good! Yozo_office print with no problem!

Excellent! Is that with the Gutenprint driver? Will it also print with the HP Postscript driver from page 32?

Yes!! Thank you very much!

[01micko]

Beta 6 is out everyone!

Barry's a bit crook and probably forgot to announce here.

Anyway, I did a cheat frugal using Lilo on my slackware box which has a SiS card. Getting a bit long in the tooth now and res is not correct on first boot with widescreen monitor, native res of 1360x768, it boots to 1280x800 which shits it left and the taskbar is out of view. I tested the thing in quicksetup but I knew it would fail with the 1280x720@75Hz because older flat panels usually only handle 60Hz. So I tested with xrandr and 1280x720 works, so I adjusted the /etc/X11/xorg.conf and it's now all good.

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

Chip description:
0.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
oem: SiS
product:

X Server: Xorg Driver used: sis

X.Org version: 1.11.3
dimensions: 1280x720 pixels (342x191 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
679 frames in 5.0 seconds = 135.726 FPS
759 frames in 5.0 seconds = 151.743 FPS
745 frames in 5.0 seconds = 148.989 FPS
# export vblank_mode=0
# glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
714 frames in 5.0 seconds = 142.695 FPS
735 frames in 5.0 seconds = 146.940 FPS
766 frames in 5.0 seconds = 153.081 FPS

Summary
-------

-Computer-
Processor : Intel(R) Celeron(R) CPU 2.66GHz
Memory : 1001MB (192MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue Sep 11 12:39:03 2012
-Display-
Resolution : 0x0 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 0x300)
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH - SiS SI7012
-Input Devices-
AT Translated Set 2 keyboard
ImPS/2 Logitech Wheel Mouse
Power Button
Power Button
PC Speaker
-Printers (CUPS)-
CUPS-PDF : <i>Default</i>
-SCSI Disks-
ATA WDC WD800JB-00JJ
HL-DT-ST DVDRAM GSA-H44N
Seagate STT8000A

Operating System
----------------

-Version-
Kernel : Linux 3.2.28 (i686)
Compiled : #1 SMP Thu Aug 23 10:19:45 GMT-8 2012
C Library : GNU C Library version 2.15 (stable)
Default C Compiler : Unknown
Distribution : Unknown distribution
-Current Session-
Computer Name : puppypc11327
User Name : root (root)
Home Directory : /root
Desktop Environment : Unknown
-Misc-
Uptime : 9 minutes
Load Average : 1.04, 1.19, 0.68

-----------------------------------------------------------------------

Just a note

The graphics in this thing are problematic with wary/racy and vesa always gets chosen, often resulting in "out of range" messages on the monitor. Since KMS seems to be working right now, there is much better performance and it at least boots to a usable desktop. Perhaps if I were using an old CRT ,which may be a better match for the card, I'd get even better performance. So don't take the above as a complaint, I am happy I get a semi-usable desktop

Thanks

[technosaurus]

attempt to blindly add btrfs to guess_fstype (no btrfs drives here to test on)... also reduced binary size from 18k to 11k by replacing printf with write (its still faster than blkid) ... also fixed? some bad errors in the adfs code
... so if this works I got it from xfsprogs/libdisk/fstype.{c,h} and there were some more available (gfs was one)

[Billtoo]

I did a manual frugal install to the hard drive.

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

Chip description:
0.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT]
(rev a1) oem: NVIDIA
product: G84 Board - p402h00 Chip Rev

X Server: Xorg Driver used: nvidia

X.Org version: 1.11.3
dimensions: 1440x900 pixels (411x263 millimeters)
depth of root window: 24 planes

Computer
Processor 4x Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Memory 8310MB (297MB used)
Display
Resolution 1440x900 pixels
OpenGL Renderer GeForce 8600 GT/PCIe/SSE2
X11 Vendor The X.Org Foundation
OpenGL
Vendor NVIDIA Corporation
Renderer GeForce 8600 GT/PCIe/SSE2
Version 3.3.0 NVIDIA 295.75
Direct Rendering Yes
# glxgears
50502 frames in 5.0 seconds = 10100.332 FPS
50493 frames in 5.0 seconds = 10098.571 FPS
50541 frames in 5.0 seconds = 10108.093 FPS
Multimedia video controller Internext Compression Inc iTVC16 (CX23416)
Video Decoder (rev 01)

I installed VLC-2.0.3 and XBMC-11.0 from ppm with no problems, VLC
works with my Hauppauge pvr card.

This new beta is amazing, thanks for making it that way.

[James C]

Quick manual frugal install of 5.3.93 on my trusty Athlon XP box. Looking really solid.

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

Chip description:
0.0 VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2

X Server: Xorg Driver used: nouveau

X.Org version: 1.11.3
dimensions: 1440x900 pixels (380x238 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.
1442 frames in 5.0 seconds = 288.320 FPS
2227 frames in 5.0 seconds = 445.371 FPS
2091 frames in 5.0 seconds = 418.099 FPS
2204 frames in 5.0 seconds = 440.796 FPS
2251 frames in 5.0 seconds = 449.951 FPS
2182 frames in 5.0 seconds = 436.246 FPS

-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (188MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 11 Sep 2012 02:25:11 AM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Mesa DRI nv18 x86/MMX+/3DNow!+/SSE
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235

[Karl Godt]

attempt to blindly add btrfs to guess_fstype (no btrfs drives here to test on)... also reduced binary size from 18k to 11k by replacing printf with write (its still faster than blkid) ... also fixed? some bad errors in the adfs code
... so if this works I got it from xfsprogs/libdisk/fstype.{c,h} and there were some more available (gfs was one)

Technosaurus , seems to work :

bash-3.2# ./guess_fstype /dev/ram5
btrfs
bash-3.2# guess_fstype /dev/ram5
unknown

!

One tiny feature to add to guess_fstype :
[*] Force extended block device numbers and spread them
config DEBUG_BLOCK_EXT_DEVT
bool "Force extended block device numbers and spread them"
depends on DEBUG_KERNEL
depends on BLOCK
default n
help
BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
YOU ARE DOING. Distros, please enable this and fix whatever
is broken.

Conventionally, block device numbers are allocated from
predetermined contiguous area. However, extended block area
may introduce non-contiguous block device numbers. This
option forces most block device numbers to be allocated from
the extended space and spreads them to discover kernel or
userland code paths which assume predetermined contiguous
device number allocation.

Note that turning on this debug option shuffles all the
device numbers for all IDE and SCSI devices including libata
ones, so root partition specified using device number
directly (via rdev or root=MAJ:MIN) won't work anymore.
Textual device names (root=/dev/sdXn) will continue to work.

bash-3.2# ls -l `rdev |cut -f1 -d' '`
brw-r--r-- 1 root adm 259, 786432 2012-09-11 09:20 /dev/sda3
bash-3.2# ./guess_fstype /dev/sda2
unknown

[rerwin]

Having 'sync' in any module-loading code that is called by the kernel, can break things. Sometime ago I took out all syncs.

Besides, sync only flushes the files to the physical drive. Prior to flushing, the files are in RAM buffers and are accessable as per normal.

So, I suggest that the solution to your problem can be found in some other way.

Thank you, Barry, for the info about 'sync' in module-loading code. It has led me to the solution! The pinstall.hsfmodem.sh script had 'sync' commands in it, which when removed allows the package to detect the HSF modem reliably. I have replaced the HSF (woof) package on page 33 with the cleaned up version.
http://www.murga-linux.com/puppy/viewto ... 304#650304

I had a similar problem with Precise for the XO laptops (3.3.8-olpc kernel) failing to find the libertas wireless firmware in both XO-1 (usb8xxx) and XO-1.5 (libertas_sdio) when rc.update was running, ie in the 1st and 2nd boot and after an update.

What unexpectedly solved the problem was (looking for more info) to boot with "loglevel=7"!!!
I doubt is your loglevel 3 kernel patch that generates the problem. I would suspect a race issue alleviated by the (slower) loglevel 7 boot sequence.

Mavrothal, thanks for your info on your similar problem. That suggests that the apparent "fix" was due to added activity changing the timing of things. If you have any syncs left in your code, you might try removing them.

Learning by making public mistakes. Whatever works.
Richard

[broomdodger]

IBM ThinkPad x30 1200 MHz 768 MB

wary5300 and racy5300 both work great

precise 5393 manual frugal
+ boot and work great with NO save file
- will NOT boot with save file = black screen
! all versions same black screen with save file

[technosaurus]

Excellent, there is a gzipped patch in the tarball (though the sources are already patched) to upload to bkhome/sources. The extended spread block devices doesn't seem worth the efforts considering the targets. However the ARM systems may ship with additional default file systems that we could try to support (specifically various flash file systems)

attempt to blindly add btrfs to guess_fstype (no btrfs drives here to test on)... also reduced binary size from 18k to 11k by replacing printf with write (its still faster than blkid) ... also fixed? some bad errors in the adfs code
... so if this works I got it from xfsprogs/libdisk/fstype.{c,h} and there were some more available (gfs was one)

Technosaurus , seems to work :

bash-3.2# ./guess_fstype /dev/ram5
btrfs
bash-3.2# guess_fstype /dev/ram5
unknown

!

One tiny feature to add to guess_fstype :
[*] Force extended block device numbers and spread them
config DEBUG_BLOCK_EXT_DEVT
bool "Force extended block device numbers and spread them"
depends on DEBUG_KERNEL
depends on BLOCK
default n
help
BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
YOU ARE DOING. Distros, please enable this and fix whatever
is broken.

Conventionally, block device numbers are allocated from
predetermined contiguous area. However, extended block area
may introduce non-contiguous block device numbers. This
option forces most block device numbers to be allocated from
the extended space and spreads them to discover kernel or
userland code paths which assume predetermined contiguous
device number allocation.

Note that turning on this debug option shuffles all the
device numbers for all IDE and SCSI devices including libata
ones, so root partition specified using device number
directly (via rdev or root=MAJ:MIN) won't work anymore.
Textual device names (root=/dev/sdXn) will continue to work.

bash-3.2# ls -l `rdev |cut -f1 -d' '`
brw-r--r-- 1 root adm 259, 786432 2012-09-11 09:20 /dev/sda3
bash-3.2# ./guess_fstype /dev/sda2
unknown

[oldyeller]

Beta6 is working great on my Dell D430. frugal install

The ppm does work much faster and I like the notice of the dependences will searching for them.

[Sage]

B6 is generally working OK, but not on an AMD1600 with 512Mb - first failure at 'loading....' observed with any release direct from BK. Machine checks out with most other distros including previous betae (presuming that's the correct plural of the Latin spelling for a Greek word?!).

[LateAdopter]

Hello BarryK

I have installed the AMD fglrx video driver using the amd-driver-installer-12.6-legacy-x86.x86_64.run

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

Chip description:
5.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4200]
oem: ATI ATOMBIOS
product: RS880 01.00

X Server: Xorg Driver used: fglrx

X.Org version: 1.11.3
dimensions: 1600x1200 pixels (423x317 millimeters)
depth of root window: 24 planes


At some point, when I was fiddling about trying to make the installer work, I had an error from: dpkg on --print-architecture.

It seems that dpkg is provided by BusyBox.

I installed the real dpkg from the Ubuntu repo and the error went away.

Once I got the installer to run without error, I did not need to do anything special to get the driver to work.

EDIT: I have since done a fglrx install with a new savefile and there were no errors from dpkg and fglrx istalled correctly.

[Sage]

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.

[shinobar]

how do I adjust for the bold style in precise?

http://www.murga-linux.com/puppy/viewto ... 207#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?

[rerwin]

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

[majorfoo]

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.

[majorfoo]

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

Now works