Wary Puppy 0.9.4 (094) feedback

[Billtoo]

Running 094 from flash drive:

On first boot retrovol needs to be configured, no sliders were set so
no sound.
I chose probe at xorgwizard and chose the proper resolution but x
wouldn't start so I ran the wizard again and chose a lower resolution
of 1440x900 which worked.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: NVIDIA
product: GT216 Board - 0682vb12 Chip Rev

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#

Nexuiz won't start.

I rebooted to create a save file and load wary_devx_094.sfs and
kernel_src-2.6.31.14-patched.sfs.One more reboot and then exited to the prompt
and ran NVIDIA-Linux-x86-260.19.12.run which I had downloaded from the nvidia
site.
Ran xorgwizard when it was finished and chose the nvidia driver.
Resolution is now 1920x1080
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: NVIDIA
product: GT216 Board - 0682vb12 Chip Rev

Driver used by Xorg:
nvidia

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#

Nexuiz plays at proper resolution of 1920x1080 with effects set to ultra.
So hardware acceleration is working.

The video upgrade wizard says that I've already upgraded, in the next section
it advises to go to the Nvidia site and download a driver.

It's looking good now

[Billtoo]

I'm running 094 on a 2gb flash drive.
I ran xorgwizard and chose probe and this time it used the nv driver
at the correct resolution of 1440x1900

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: NVIDIA
product: G84 Board - p402h00 Chip Rev

Driver used by Xorg:
nv

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#

Nexuiz will start but it's unplayable.

I used the same procedure as before to load the devx,kernel sources sfs, and
NVIDIA-Linux-x86-260.19.12.run files.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: NVIDIA
product: G84 Board - p402h00 Chip Rev

Driver used by Xorg:
nvidia

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#

Nexuiz runs at 1440x900 resolution with effects set to ultra.

So I'm able to get accelerated graphics on all 3 computers, 2 nvidia and 1 ati
which is nice

[rerwin]

I have attached the missing piece for correct detection of agrmodem variants, to match Barry's implementation of the agrmodem directory structure.

In addition, the attached package has a possible fix for HDA modems using the HSF Conexant chipset. If the module hsfhda gets loaded in addition to snd-hda-intel, the device is set as ttySHSF0 and the slmodemd daemon is not started. I cannot test this part, so please report any problem with it.

Regarding the renaming of the Agere and Intel 537 drivers, to hide them: I recommend that the 11c11040 variant be delivered with its correct (.ko) name and all others as .koHIDE. The 11c11040 variant generates modalias entries, so must be available to depmod. None of the others create modaliases.

The reason to hide all the Intel 537 variants is because they are each about 4 megabytes in size. Each rename makes a copy of the module in the top (read-write) layer of the file system, consuming 4 more MB of pupsave-file space! With all initially hidden, utilization of one of the variants would use 4 MB. If another variant had to be hidden (renamed), that would use an additional 4 MB! Of course, this is not an issue with a full installation.

One other thing: the Intel536 module need not be in its own directory, since there are no variants. It can be directly under intelmodem.

UPDATE 10/31/2010: Uploaded replacement attachment with refined Agere detector and new Intel 537 variant detector. Also separated alsa.conf file to separate the automatically detected sound card aliases from those created by the ALSA wizard (alsaconf). The automatically (backend modprobe) generated file is alsa_cards.conf. Card number determination now avoids using any "snd-card" number already taken by the wizard and included in alsa.conf. This retains the wizard's number(s) across bootups, which regenerate the numbers for PCI sound cards. In "real life", the wizard probably would be used only if no PCI sound cards are installed; but this is for "just in case" that is not true. Later, I re-uploaded after download number 2 with a resolution of Barry's issue with the pctel modem driver and its dependencies.

UPDATE 11/2/2010: Uploaded replacement attachment, after download number 8, to add support for already switched USB modems which would not otherwise have their driver loaded if that depends on usb_modeswitch to initiate the loading (e.g., some Vodaphones).

UPDATE 11/4/2010: Uploaded replacement attachment that adds to "-3" support for the HSF modems. The wary driver appears broken. I was unable to even compile it! This new driver version is built from the latest release. But it may not work for HDA HSF modems, because I am uncertain of the status of the HSF-HDA patch to the ALSA HDA driver.

UPDATE 11/5/2010: Re-uploaded the "-4" modem package after download number 4, to add updates to the HSF, HCF and DGC firmware tarballs, in support of the new versions of those drivers. Although I have tested HSF and DGC modems, I do not have an HCF modem for testing.
Richard

[broomdodger]

Running great.

dell inspiron 5150
-Computer-
Processor : Mobile Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory : 1034MB (92MB used)
Operating System : Puppy Linux 0.09
User Name : root (root)
Date/Time : Thu 28 Oct 2010 08:59:44 PM PDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation

205637 ~# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: NVIDIA
product: NV34 Board - p135nz Chip Rev

Driver used by Xorg:
nv

Video mode used by Xorg:
Resolution: Depth 16 Depth: "Display"

[myman_05]

Happen when click save button. (see attachment)

VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: Copyright 1998 TRIDENT MICROSYSTEMS INC.

Driver used by Xorg:
trident

Video mode used by Xorg:
Resolution: Depth 16 Depth: "Display"

...the above also recorded in /tmp/report-video

except this bug averything else running great.

TQ

[myman_05]

Fresh frugal install.

See attachment

[Sit Heel Speak]

Well, I hope this is just some simple thing I'm forgetting to do, so everyone please do feel free to point out the obvious, but...

Running from live CD, and the .iso tested good for md5sum both when downloaded and in PBurn, on a homebrew box. Intel D865GSA mainboard, a correct P4-931 single core CPU for it, 1 GB ram. It has an nVidia FX5200 video card added-in (i.e. not using the mainboard's integrated Intel Extreme Graphics). I've been running Windows 98SE essentially 24/7 on it for a month now without a hiccup.

xorgwizard found the nv driver for it OK. Setup gave no glitches.

One initial turn-off: response to mouseclicking on desktop icons requires an exact hit on the center of the icon, and there is a distressing lag time before Seamonkey or whatever appears. Well, "distressing" is a relative term. I'll put it this way: wary-094 does not have the essentially instantaneous response of a t2 Quirky which I woof-built on September 5th. Nor is wary-094 as fast as tazOC's current Lighthouse Pup, version 5.00F, when running under Openbox.

The box is connected to the net and my home LAN (my LAN is all wired only) by the mainboard's integrated Realtek 8139. The 8139 works in previous Puppies and in Windows 98SE.

8139too shows in lsmod.

Dougal's network setup is able to find a live network.

DHCP does not succeed. DHCP service is provided by a DLink DI-604 router, between the box and my DSL modem. DHCP works as advertised on both Lighthouse Puppy 5.00F and the woof-built t2 Quirky.

Setting a fixed IP of 192.168.0.7:255.255.255.0, with gateway and DNS at the usual 192.168.0.1, succeeds. Or so the Network Wizard says.

Seamonkey doesn't work. No indication of any network connection. Tried every possible Proxy setting. No joy.

Ping no workee, either.

Can anyone see something obvious I forgot to do?

[tlchost]

Downloaded iso twice to create bootable USB with same results at bootup:

puppy pfix=ram
At first boot I see

Pausing Pausing
searching deeper, sub-sub-folder in partitions
above sequence repeats

boot partition not found
Dropping out to initial ramdisk console
/bin/sh: can't access tty; job control turned off

Thom

[Sage]

Nice. Yes - snappy. Everything seems to work, even on 'new' stuff. Best yet.
Installing Firefox leads to two 'missing' files, allegedly, - a lib one which I didn't note down and, strangely, an alsa file. FF still not showing in menu. However, everything works including sound (not muted) and FF from console.

SHS: Never, ever use Intel kit! Some reports of DLink issues? Which nV driver?! It may be detecting the onboard video chip? Sever the power line with a scalpel and have done with it!

[Sit Heel Speak]

SHS: Never, ever use Intel kit! Some reports of DLink issues? Which nV driver?! It may be detecting the onboard video chip? Sever the power line with a scalpel and have done with it!

The DLink is fine, the nv driver is the one supplied with the live CD, these are not where the problem lies.

I quite agree with you, Sage my friend, that Intel ATX mainboards have been decidedly second-rate for about three years now.

But neither Windows 98SE (when correctly installed, using my fanatical 32-step procedure) nor the other two Puppies above-named, are slow on it like wary-094 is.

And the 8139too nic driver works on this box using these Puppies, but apparently does not work in wary-094.

[Sage]

about three years

thirty three? Remember all those recalls back as far as 286s, PI s, etc., all those chip microcode bugs appearing in full diagnostics lists?! Amazing that their shareholders have tolerated their behaviour for so long; most of them are users as well as receivers of dividends! Foot-shooters all.
So, sorry, my old cobber, everything works for me - you'll have to wait till the smart guys pick up the thread.

[tronkel]

Good version. LibreOffice works now. This is a keeper for me.

Only thing that could be tidied up is the 2.07 Seamonkey version. This version has been a tad unstable in general, but is supposed to have been sorted in the later versions. I compiled the last but one - version (2.0.9) in Wary 0.92 and this appears to be better in this regard.

In the meantime, Seamonkey has been bumped to 2.0.10 and Wary 0.9.4 has been born. So maybe a good time for another compile and pet build of this latest version.

I'm off to Bohemia for a week, but if I get the time before I go, I'll get it compiled again.

[gjuhasz]

I see that the Video Upgrade Wizard is displaying some wrong information.

In my case it is a bit worse. Video Upgrade Wizard is right. It tells me that my Geforce 6200 is not supported by the available nvidia drivers. It's weird because I run nvidia driver for all other puppies I installed and test (with some exceptions such as Quirky and Zen, for which I don't have driver compiled.)
Those drivers are compiled by forum members gray, JustGreg and/or 01Micko.
For some unknown reason, Barry's nvidia pets have never been applicable for my nvidia GeForce 6200 card. I always had to wait for others' pets - for example 01Micko's pet was OK for the previous wary.
Be sure I always follow the instructions displayed.

Barry, just FYI, I see that others use your driver(s) successfully.
Maybe they know better what to do differently to avoid black screen.

[peebee]

Wonderful - Agere HDA modem works OOTB with this Puppy - well done Barry and rerwin. Have also applied rerwin's pet but as my modem is "the default" 11c11040 this is not a real test.

Couple of funnies:

1. the pupsave tray indicator is only showing 1 green bar for a 512MB pupsave with >490MB unused

2. during the bootup sequence kernel module loading the following error is being displayed:

e1000e pci_enable_pcie_error_reporting failed 0xfffffffb

Cheers
Peter

[tlchost]

Created CD from iso and then used that to create bootable USB.

Bootable USB works...but it is most inconvenient to make a cd and then
use that to create bootable USB drive.

My goal is to have bootable USBs to distribute to senior citizens allowing them to run Eldy http://www.eldy.eu/

To date Eldy does not operate correctly on any version of Puppy I have tried, although others have reported success with Ubuntu.

Puppy and Eldy would be an ideal combination.

Thom

[DaveS]

So somebody tell me please: what do I need to do to compile seamonkey for wary? How would I begin etc?

[tronkel]

Get the latest Seamonkey 2.0.10 pet for Wary 0.9.4 from this thread:

http://www.murga-linux.com/puppy/viewto ... 032#462032

[DaveS]

Is this the same configuration (options) as the current wary version, or is Barry's configured differently?

[tronkel]

@DaveS

See this thread for compiling seamonkey for Wary
http://www.murga-linux.com/puppy/viewto ... 816#460816

How about having a go at compiling Seamonkey 2.1?
Source is available at the mozilla.org website.

I've been having a go with compiling the latest Firefox for Wary. Seems much more difficult than compiling Seamonkey. Big problems with compile-time dependencies.

I did manage to get a functioning build for Firefox 4 Beta (Minefield) in Ubuntu (64 bit though)

This looks very interesting. Would be excellent to get this built for Puppy/Wary. Nice new interface features and fast. Seems stable as well.

[DaveS]

How about having a go at compiling Seamonkey 2.1?
Source is available at the mozilla.org website.

I did do a normal install for 2.1 but flash performance fell below acceptable on some sites, so I left it. Figured I would wait for a non beta.